QA testing

Revision as of 13:43, 10 November 2017 by Helen Foster (talk | contribs) (QA testing latest update - 100% in 3.4 cycle)

Jump to: navigation, search

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: A 100% pass rate was obtained in Moodle 3.4 QA testing. Many thanks to all our QA testers.

Getting involved

Would you like to help with QA testing? If so, please make sure you have created an account in the Moodle tracker, then contact Helen. Also, make sure 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.

Running tests

  1. Select a test from the list. When viewing a test, if you wish, you can click the 'Assign to me' link on the right, so that nobody else chooses the same test to run. (If you then find you are unable to run the test, you can assign the issue back to 'Unassigned'.) Please note:
    • Only assign an issue to yourself which no one else is testing (Assignee = Unassigned).
    • Only assign one issue at a time unless you plan to test a number of related issues within the next 24 hours. In other words, don't assign several issues to yourself then do nothing for several days. ;-)
    • The label test_server_required indicates issues that can't be tested on the QA testing site. The label credentials_required indicates that credentials such as an OAuth 2 service client ID and secret are required.
  2. Using either the Moodle QA Testing Site or your own test site running the latest Moodle 3.4 beta (available from Git on the integration/master branch git:// with debugging set to developer, perform each of the steps listed in the test. Please test using both the Clean and Boost themes.
  3. Choose an appropriate workflow action:
    • Pass - Test runs perfectly. Add comment such as feedback about a new feature, browsers used for testing (if applicable), or simply "This test passes - yippee!"
    • Fail - Something doesn't work, or you obtain debugging messages. Add comment describing the step that doesn't work. If in doubt whether to pass a test, give it a fail and add a comment describing your doubts.
    • Obsolete - Test is no longer relevant in the current Moodle version. Add comment explaining why.

If you notice that the test description is out-of-date, add a comment suggesting how it can be updated and type @Helen Foster then select Helen from the menu below the input box. Alternatively, if you'd like to help with updating the test yourself, see below.

Moodle QA Testing Site

The Moodle QA Testing Site is updated daily at around 13:00 UTC with the latest bug fixes to enable you to re-run QA tests.

To prevent the site being used for sending spam, no emails are sent from it. Thus, tests involving email cannot be run using the Moodle QA Testing Site. (If such tests are attempted, an email debug message is displayed. This is not a bug but rather expected behaviour.)

Manager, teacher and student accounts are provided. Please contact Helen if you would like admin access to the Moodle QA Testing Site for running certain tests.

Failed tests

So you ran a test and it failed? Congratulations on finding a bug! Please do the following.

  1. Click the Fail button at the top of the page.
  2. Add a comment to the QA test stating that there was a problem and that you will report it as a Moodle bug.
  3. Note the MDLQA number; it will be something like MDLQA-448.
  4. Try searching for whether the bug has been reported previously, and if not create a new issue for it (as described in Tracker introduction).
  5. In the new Moodle (MDL) issue select 'Link' from the 'More actions' dropdown menu.
    Linking to the QA issue in the tracker
  6. Link to the QA test by selecting 'blocks' as the link type, entering the MDLQA number that you noted earlier, and optionally adding a comment.
    Adding details for a link to the QA issue
  7. Give the issue the label 'mdlqa'.
  8. (Optional) Add yourself as a watcher to the MDL issue so that you receive email notification when the issue is fixed.
  9. When the MDL issue is fixed, hopefully within a day or two, the QA test can be reset and can then be run again.

Resetting tests

Note for integrators:

After integrating a fix,

  1. Reset the MDLQA test, adding a comment.
  2. Remove the 'mdlqa' label from the MDL issue.
  3. If the issue doesn't have testing instructions, pass it with message "Will be tested by MDLQA-XXXX".

The tester will then receive email notification that the bug is fixed and will hopefully decide to run the test again soon.

Suggested comment:

Thanks for running this QA test. The bug causing it to fail has now been fixed, so the test can be reset and run again.
Please note that if you are using for testing, you will need to wait for the site to be updated at 13:00 UTC in order to test the bug fix.

Updating tests

QA tests often become out-of-date due to new developments. If you would like to help with updating tests, you'll need to be a member of the test writers group in the Tracker. Please contact Helen about being added.

To update a QA test:

  1. Search for the master copy of the test - with affects version as 'Master copy' and MDLQA-1 as parent.
  2. Edit the test description.
  3. Optional: Add a comment describing your edit.

Writing new tests

Would you like to help with writing new QA tests? If so, as for updating tests, 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:

  1. Choose an issue from the closed qa_test_required-labelled issues
  2. Create a sub-task of MDLQA-1
  3. Select Master copy as affected version
  4. Select appropriate components including at least one of the following: User, Student, Teacher, Administrator
  5. Set assignee as unassigned
  6. Write the test (usually between 3 and 10 steps). It's a good idea to try doing the steps yourself as you write the test.
  7. Go to the MDL issue and create a ‘has a QA test’ link to the new QA test, adding a comment “Thanks for this improvement which is now covered by the QA test MDLQA....”, and if necessary remove the qa_test_required label. Make sure that all QA tests are linked back to a corresponding MDL issue.

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.

See also

Comments on tests from previous QA cycles: