Acceptance testing/Contributing automated tests: Difference between revisions
From MoodleDocs
(Created page with "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: # Check the list o...") |
No edit summary |
||
| Line 3: | Line 3: | ||
# Check the list of critical features in the MDLQA project | # Check the list of critical features in the MDLQA project | ||
# 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 | # 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 | ||
#* Choose a '''Blocker''' issue https://tracker.moodle.org/ | #* Choose a '''Blocker''' issue https://tracker.moodle.org/issues/?jql=parent%20%3D%20%4DDLQA-1%20and%20priority%20%3D%20Blocker | ||
#* When all '''Blocker''' issues are converted we can begin with the '''Critical''' ones | #* When all '''Blocker''' issues are converted we can begin with the '''Critical''' ones https://tracker.moodle.org/issues/?jql=parent%20%3D%20%4DDLQA-1%20and%20priority%20%3D%20Critical | ||
#* When all '''Critical''' issues are converted we can begin with the '''Major''' ones | #* When all '''Critical''' issues are converted we can begin with the '''Major''' ones https://tracker.moodle.org/issues/?jql=parent%20%3D%20%4DDLQA-1%20and%20priority%20%3D%20Major | ||
#* MDLQA issues with priority '''Minor''' and '''Trivial''' can be hard or not possible to automate as they require integration with other systems, codebase modifications or other actions outside the browser scope. | #* MDLQA issues with priority '''Minor''' and '''Trivial''' can be hard or not possible to automate as they require integration with other systems, codebase modifications or other actions outside the browser scope. | ||
# Fill a new issue in MDL project | # Fill a new issue in MDL project | ||
Revision as of 11:01, 9 July 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:
- Check the list of critical features in the MDLQA project
- 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
- Choose a Blocker issue https://tracker.moodle.org/issues/?jql=parent%20%3D%20%4DDLQA-1%20and%20priority%20%3D%20Blocker
- When all Blocker issues are converted we can begin with the Critical ones https://tracker.moodle.org/issues/?jql=parent%20%3D%20%4DDLQA-1%20and%20priority%20%3D%20Critical
- When all Critical issues are converted we can begin with the Major ones https://tracker.moodle.org/issues/?jql=parent%20%3D%20%4DDLQA-1%20and%20priority%20%3D%20Major
- MDLQA issues with priority Minor and Trivial can be hard or not possible to automate as they require integration with other systems, codebase modifications or other actions outside the browser scope.
- 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 link to the MDLQA-NNNN
- Follow the process to add new features or new scenarios to existing features
- https://docs.moodle.org/dev/Acceptance_testing#Writing_features
- Use the check list to discard basic issues (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)
- Feature files 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
