Majic Projects
Majic Ansible Roles
Go to the previous open issue
Go to the previous issue (open or closed)
star_faded.png
Please log in to bookmark issues
icon_project.png Majic Ansible Roles / Closed Feature request MAR-29 Tests for php_website role
action_vote_minus_faded.png
0
Votes
 action_vote_plus_faded.png
Go to the next issue (open or closed)
Go to the next open issue
This issue has been closed with status "Closed" and resolution "RESOLVED".
Issue basics
  • Type of issue
    Feature request
  • Category
    Not determined
  • Targetted for
    1.6.0
  • Status
    Closed
  • Progress
  • Priority
    Not determined
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (0)
There are no items
People involved
Times and dates
  • Posted at
  • Last updated
  • Estimated time
    Not estimated
  • Time spent
    4 hours
    Click here to see time logged against this issue
Issue details
  • Resolution
    RESOLVED
Attachments (0)
There is nothing attached to this issue
Duplicate issues (0)
This issue does not have any duplicates
Show / hide more details »
Description

Implement tests for php_website role.

The following should be done:

  • Use Molecule for automating VM provisioning and running tests.
  • Update tasks as necessary to pass Ansible Lint checks. Introduce the skip_ansible_lint tag on relevant tasks where linting should be skipped.
  • Apply minimal fixes to issues discovered during testing.
  • Use dedicated FQDN for websites (different from server name).
  • It might be possible to use a single server for testing (with multiple websites on it).
  • When creating the tests, keep in mind the following:
    • Mandatory parameters should be tested.
    • Optional parameters should be tested.
    • Make sure to test ability to pass-in custom headers to user script.
    • Make sure to test some basics by deploying a couple of simple PHP pages.
    • Make sure to test mail forwarding (for application user) using local accounts.
    • Make sure to test dedicated TLS private key/certificate is used (different from default one).
    • Test on Debian Jessie (64-bit) only.
Todos (0 / 0)
Options
There are no comments