Note:

If you want to create a new page for developers, you should create it on the Moodle Developer Resource site.

Acceptance testing/Contributing automated tests: Difference between revisions

From MoodleDocs
No edit summary
No edit summary
Line 10: Line 10:
#* Description: Automate MDLQA-NNNN - I'm the MDLQA description
#* Description: Automate MDLQA-NNNN - I'm the MDLQA description
#* Component 'Automated functional tests' and the MDLQA component
#* Component 'Automated functional tests' and the MDLQA component
#* Add a link to the MDLQA-NNNN
#* Add a '''will help resolve''' link to the MDLQA-NNNN
# Follow the process to add new features or new scenarios to existing features
# Follow the process to add new features or new scenarios to existing features
#* https://docs.moodle.org/dev/Acceptance_testing#Writing_features  
#* Check the affected components current list of behat features (COMPONENTNAME/tests/behat/) to see if any of them already includes the MDLQA tests or can be slightly modified to include it
#* Use the check list to discard basic issues (https://docs.moodle.org/dev/Acceptance_testing#Features_check_list)
#* https://docs.moodle.org/dev/Acceptance_testing#Writing_features
#* Use the check list to discard basic issues when writing tests (https://docs.moodle.org/dev/Acceptance_testing#Features_check_list)
#* Add new step definitions in case there are repeated blocks of steps (https://docs.moodle.org/dev/Acceptance_testing#Adding_steps_definitions)
#* Add new step definitions in case there are repeated blocks of steps (https://docs.moodle.org/dev/Acceptance_testing#Adding_steps_definitions)
#* Feature files should be backported as much as possible
#* Feature files and changes in them should be backported as much as possible
#* Include MDLQA-NNNN and short description of what is being automated to the commit message/s where the .feature files are added/edited
#* Include MDLQA-NNNN and short description of what is being automated to the commit message/s where the .feature files are added/edited

Revision as of 02:29, 11 October 2013

If you want to help the effort of automating the current list of MDLQA issues that we run manually before each major release these are the steps to follow:

  1. Check the list of critical features in the MDLQA project
  2. Choose one of the listed MDLQA issues to convert it to an automated test, the issues are prioritized using the Blocker, Critical, Major, Minor, Trivial scale
  3. Fill a new issue in MDL project
    • Description: Automate MDLQA-NNNN - I'm the MDLQA description
    • Component 'Automated functional tests' and the MDLQA component
    • Add a will help resolve link to the MDLQA-NNNN
  4. Follow the process to add new features or new scenarios to existing features