Testing instructions guide: Difference between revisions
From MoodleDocs
Modified to apply the {{Template:CurrentlySupportedThemes}} |
Remove wip and add point about adding commands (git, sql...) to the testing instructions. Signed by iTeam. |
||
| Line 1: | Line 1: | ||
This page has suggestions for developers on how to write good testing instructions for the weekly [[Testing of integrated issues|testing of integrated issues]]. | This page has suggestions for developers on how to write good testing instructions for the weekly [[Testing of integrated issues|testing of integrated issues]]. | ||
| Line 15: | Line 11: | ||
# Setup requirements. If so, provide a link to the documentation e.g. https://docs.moodle.org/en/OAuth_2_services if necessary writing something in the dev docs. | # Setup requirements. If so, provide a link to the documentation e.g. https://docs.moodle.org/en/OAuth_2_services if necessary writing something in the dev docs. | ||
# Whether testing involves git/shell interaction, SQL operations... (commands in general), don't assume the tester knows how to perform that stuff. Instead, add them explicitly to the instructions. | |||
# Whether testing may be done using the [https://qa.moodle.net/ Moodle QA testing site]. | # Whether testing may be done using the [https://qa.moodle.net/ Moodle QA testing site]. | ||
# Whether multiple themes {{Template:CurrentlySupportedThemes}} should be used. | # Whether multiple themes {{Template:CurrentlySupportedThemes}} should be used. | ||
Revision as of 17:12, 3 September 2019
This page has suggestions for developers on how to write good testing instructions for the weekly testing of integrated issues.
We recommend that you:
- Number the steps in your test, and make use of sub-lists.
- Promote test validations - Confirm, Verify or Ensure - should be in bold so that they are easily identifiable.
- Only put one test validation on each line - A test step should only have one test validation at a time.
- Make use of the Jira Markdown formatting.
In addition, the following items may be included:
- Setup requirements. If so, provide a link to the documentation e.g. https://docs.moodle.org/en/OAuth_2_services if necessary writing something in the dev docs.
- Whether testing involves git/shell interaction, SQL operations... (commands in general), don't assume the tester knows how to perform that stuff. Instead, add them explicitly to the instructions.
- Whether testing may be done using the Moodle QA testing site.
- Whether multiple themes (current themes being Boost and Clean for old versions and Boost and Classic for 3.7 and up) should be used.
- Whether more than one browser should be used. (Tester should specify which browsers they used.)
- Whether extra testing around the issue is required.
