Note:

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

Testing of integrated issues: Difference between revisions

From MoodleDocs
(setting yourself as QA assignee)
(notes)
Line 11: Line 11:
# If test passes, close the corresponding MDL issue, setting a fix version of the next unreleased version and yourself as QA assignee; if test fails reopen the MDL issue
# If test passes, close the corresponding MDL issue, setting a fix version of the next unreleased version and yourself as QA assignee; if test fails reopen the MDL issue


==Notes==
* For issues which require an Oracle installation for testing, Petr, Eloy and Apu have one


[[Category:Quality Assurance]]
[[Category:Quality Assurance]]

Revision as of 15:17, 11 January 2011

Note: This page is for analysing and developing our weekly testing of code added to the integration server. It is a work-in-progress. Comments or suggestions are welcome! Please use the page comments.


Testing is an important part of the Moodle development process.

The testing process

  1. Go through the 'Ready for testing' pull requests
  2. Test the new 2.0 features/fixes on the Moodle QA Testing Site
  3. Select 'Pass test' or 'Fail test' as appropriate, adding a short description of what was tested if not obvious
  4. If test passes, close the corresponding MDL issue, setting a fix version of the next unreleased version and yourself as QA assignee; if test fails reopen the MDL issue

Notes

  • For issues which require an Oracle installation for testing, Petr, Eloy and Apu have one