|
|
| (31 intermediate revisions by 5 users not shown) |
| Line 1: |
Line 1: |
| '''Quality Assurance''' tests look at the functionality of Moodle from a user's point of view.
| | {{Moodle community}} |
| | Quality Assurance (QA) 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. | | 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. | | These tests are repeated in series of cycles, usually just before major releases. Developers and volunteer testers communicate through [[Tracker]] on what they find. More information can be found in the Development page also called [https://docs.moodle.org/dev/QA_testing QA testing]. |
| | |
| | |
| ==Getting involved==
| |
| | |
| [[Image:Qa test workflow actions.png|thumb|Testers can pass or fail QA tests and add comments]]Would you like to help with QA testing? If so, please contact [http://moodle.org/user/view.php?id=24152&course=1 Helen].
| |
| | |
| All testers are members of the testers group in the Moodle Tracker, enabling them to pass or fail QA tests and add comments.
| |
| | |
| ==Running tests==
| |
| | |
| # Select a test from the [http://tracker.moodle.org/browse/MDLQA-150 Moodle 2.0 QA Cycle 1] list (or the [http://tracker.moodle.org/browse/MDLQA/fixforversion/10422 Moodle 2.0 QA Cycle 1 overview])
| |
| # Using either the [http://qa.moodle.net/ Moodle QA Testing Site] or your own test site running the latest Moodle 2.0 version, 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''', [http://tracker.moodle.org/secure/CreateIssue!default.jspa?pid=10011 creating a new 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 today's version of Moodle 2.0 for testing. The [http://qa.moodle.net/ Moodle QA Testing Site] is updated daily.
| |
| | |
| When you pass or fail a test, you are automatically named as the assignee.
| |
| | |
| ==Failed tests==
| |
| | |
| So you ran a test and it failed? Congratulations on finding a bug!
| |
| | |
| # Make sure that the problem is reported as an MDL issue 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.)
| |
| | |
| ==Feedback==
| |
| | |
| Feedback on all aspects of our QA testing process is welcome. If you have any questions or comments, please post in the [http://moodle.org/mod/forum/view.php?id=56 Testing and QA forum] in Using Moodle.
| |
| | |
| [[Category:Quality Assurance]]
| |
Quality Assurance (QA) 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. Developers and volunteer testers communicate through Tracker on what they find. More information can be found in the Development page also called QA testing.
