Note:

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

Testing instructions guide: Difference between revisions

From MoodleDocs
(work in progress template, items for inclusion, category)
 
(rewording)
Line 5: Line 5:
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]].


In addition to numbered test steps, the following items may be included:
# Number the test steps.
# Test validations - Confirm, Verify or Ensure - should be in bold.
# A test step should only have one test validation.


[] 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.
In addition, the following items may be included:
[] Testing may be done using the [https://qa.moodle.net/ Moodle QA testing site]?
 
[] Testing must be done using Boost and / or Clean theme?
# 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.
[] Testing must be done using more than one browser? (Tester should specify which browsers they used.)
# Whether testing may be done using the [https://qa.moodle.net/ Moodle QA testing site].
[] Extra testing around the issue is required?
# Whether the Boost and / or Clean theme 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.
   
   
[[Category: Processes]]weekl
[[Category: Processes]]

Revision as of 13:47, 28 September 2017

Note: This page is a work-in-progress. Feedback and suggested improvements are welcome. Please join the discussion on moodle.org or use the page comments.

This page has suggestions for developers on how to write good testing instructions for the weekly testing of integrated issues.

  1. Number the test steps.
  2. Test validations - Confirm, Verify or Ensure - should be in bold.
  3. A test step should only have one test validation.

In addition, the following items may be included:

  1. 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.
  2. Whether testing may be done using the Moodle QA testing site.
  3. Whether the Boost and / or Clean theme should be used.
  4. Whether more than one browser should be used. (Tester should specify which browsers they used.)
  5. Whether extra testing around the issue is required.
Retrieved from "https://docs.moodle.org/dev/index.php?title=Testing_instructions_guide&oldid=52966"
Powered by MediaWiki