I am set up for my first Moodle QA task (see part 1); I have time set aside, music playing and am ready to go.
The First QA ticket
MDLQA-12926 CLONE – A teacher can choose a grading scale for rating glossary entries and can restrict rating to within certain dates.
This was to test Glossary functionality: that only student contributions within a specified date/time range could be graded, and graded correctly.
The test does not outline a procedure. I’m meant to figure that out – it would be too onerous to document otherwise. For this test, I used the following strategy:
- On FireFox, log into test site as teacher, set up a new glossary for the test. Allowing a 1 hour contribution range.
- On three browsers (Safari, Chrome, and Opera) log in as different students.
- Each student makes a contribution before, during and after.
- As teacher, check rating of contributions.
The QA result
It passed. Screen grabs (with green highlights indicating the tested features that passed) were added to the ticket.
Finding new bugs
I swore I saw another bug on the way through: print view of the grade layout didn’t have the glossary ratings. So I asked what to do…
If you see another bug in the process of testing, please make sure that it is reported as an MDL issue (search for it, and if you don’t find any report, feel free to create and new issue for it) then mention it in a comment in the QA test.
Discovering other bugs in the process of testing is really good, and a reason for doing manual QA testing and not just relying on automated testing.
– the Moodle Community Manager
After going back to double check, I realised given the context, it was not a bug.
Moodle Fun Time Facts:
As the bug dealt with real world times, I had to quickly learn about how this particular QA version of Moodle deals with time:
- The QA Course uses the AWST timezone for Perth, Australia (-2 hours for Melburnians).
- The Moodle QA Site gets reset every hour, on the hour. Make sure you have time to complete the test!
- The Moodle QA Site server is updated every day 13:00 or UTC (or 11pm for Melburnians).
QA’ing was quite easy despite the first QA task taking a while. It was good to figure out the timezone traps – useful in future.
What would I do differently? I’m sure the next will be quicker. It’s all about being set up right, then it’s simply a matter of simply being methodical, working through each QA task one by one.
One thing I could do differently is to use the standalone development version. This would allow me to avoid the 1 hour limit and, work through multiple related QA tests more effectively.
How did it feel? Good. The work done passed muster and good to be contributing (finally).