Aquesta pàgina forma part de la documentació de Moodle en català, tot i que no ha estat traduïda encara. Podeu contribuir obertament a les tasques de traducció. Podeu consultar la Guia d'edició de la documentació i també participar ens els debats del fòrum de traductors de la documentació a moodle.org
Quality Assurance tests look at the functionality of Moodle from a user's point of view.
Real users systematically try each feature in Moodle and test that it works in the current version of the Moodle code.
These tests are repeated in series of cycles, usually just before major releases.
QA testing latest: We'll be starting another QA cycle at the beginning of June to test Moodle 2.1 before its release on 30th June 2011.
Getting involvedHelen and ensure you're subscribed to the Testing and QA forum in order to receive QA testing news updates.
All testers are members of the testers group in the Moodle Tracker, enabling them to pass or fail QA tests and add comments.
- Select a test from the Moodle 2.0.2 QA list
- Using either the Moodle QA Testing Site or your own test site running the latest Moodle 2.0.1+, perform each of the steps listed in the test
- Choose an appropriate workflow action:
- Pass - Test runs perfectly :-)
- Fail - Indicate in a comment where the test fails and include the MDL issue number of the report of the problem, creating a new Tracker issue if necessary (see below for more details)
- Obsolete - Test is no longer relevant in the current Moodle version (unlikely for Moodle 2.0, but may occur when testing Moodle 2.1)
If in doubt whether to pass a test, give it a fail and perhaps ask someone else to have a look by adding them as a watcher then adding a comment.
Note: Always use the latest version of Moodle 2.0.1+ for testing or the Moodle QA Testing Site.
When you pass or fail a test, you are automatically named as the assignee.
So you ran a test and it failed? Congratulations on finding a bug! Please do the following:
- Make sure that the problem is reported as an MDL issue in the Tracker for developers to investigate and fix
- Add a comment to the QA test, stating the MDL issue number
- Link the MDL issue to the QA test
- (Optional) Add yourself as a watcher to the MDL issue so that you receive email notification when the issue is fixed
- When the MDL issue is fixed, the QA test can be reset
- The reset QA test can then be run again
Note for developers:
After fixing a bug, please add a comment to the linked MDLQA test thanking the tester and informing them that the test can be run again, then click the reset link. The tester will then receive email notification that the bug is fixed and will hopefully decide to run the test again soon. (Otherwise when the test is reset, it's assigned to nobody, and if the tester isn't watching the MDL issue, they won't know about the bug being fixed.)
The role of Core developers in creating tests
When a developer adds functionality to Moodle, they should also do the following.
- Write user documentation in the User docs about the new feature (this should happen as part of the normal development process). Ask someone to proof read this documentation.
- Add a feature to the Release notes (for example in the 2.1 Release notes). These features should include a link to an appropriate Tracker issue that contains testing instructions and to the user documentation for the feature.
The QA tests will be written by the Community Manager or a Test Writer based on the documentation and release notes written by the developer.
Writing new tests
Would you like to help with writing new QA tests? If so, you'll need to be a member of the test writers group in the Tracker. Please contact Helen about being added.
To create a new QA test:
- Create a sub-task of MDLQA-1
- Select Master copy as affected version
- Select appropriate components including at least one of the following: User, Student, Teacher, Administrator
- Leave the assignee as automatic (nobody)
New tests will be included in the next QA cycle.
Feedback on all aspects of our QA testing process is welcome. If you have any questions or comments, please post in the Testing and QA forum in Using Moodle.
Comments on tests from previous QA cycles: