Note:

This site is no longer used and is in read-only mode. Instead please go to our new Moodle Developer Resource site.

Testing of integrated issues

From MoodleDocs
Revision as of 17:19, 12 January 2011 by Helen Foster (talk | contribs) (The testing process: rewording)

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 and 1.9 fixes on a local site
  3. Select 'Pass test' or 'Fail test' as appropriate, adding a short description of what was tested if not obvious
  4. If the test passes, close the corresponding MDL issue, add a fix version of the next unreleased version e.g. 2.0.2 and yourself as QA assignee
  5. If the test fails, reopen the MDL issue

Notes

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