Testing of integrated issues: Difference between revisions
From MoodleDocs
Helen Foster (talk | contribs) (setting yourself as QA assignee) |
Helen Foster (talk | contribs) (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
- Go through the 'Ready for testing' pull requests
- Test the new 2.0 features/fixes on the Moodle QA Testing Site
- Select 'Pass test' or 'Fail test' as appropriate, adding a short description of what was tested if not obvious
- 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
