|
|
| (47 revisions intermèdies per 6 usuaris que no es mostren) |
| Línia 1: |
Línia 1: |
| ==Getting involved==
| | {{Moodle community}} |
| | Quality Assurance (QA) tests look at the functionality of Moodle from a user's point of view. |
|
| |
|
| Would you like to help with QA testing? If so, please contact [http://moodle.org/user/view.php?id=24152&course=1 Helen].
| | Real users systematically try each feature in Moodle and test that it works in the current version of the Moodle code. |
|
| |
|
| All testers are members of the testers group in the Moodle Tracker, enabling them to assign, comment and pass or fail [http://tracker.moodle.org/browse/MDLQA Moodle QA issues].
| | 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]. |
| | |
| ==Assigning issues==
| |
| | |
| Assuming you are a member of the testers group, the first thing to do is decide which QA tests you'd like to perform and assign them to yourself.
| |
| | |
| # Browse the lists of [[Development:Features list - activity modules|activity module tests]] and [[Development:Features list - course administration|course administration tests]] and choose some QA tests
| |
| # For each chosen test, find the operation "Assign this issue" in the left column and click the "to me" link
| |
| | |
| ==Running tests==
| |
| | |
| # Using either the [http://qa.moodle.net/ Moodle QA Testing Site] or your own test site running the latest Moodle 2.0 preview version, perform each of the steps listed in the test
| |
| # Optional: Add a comment on your findings
| |
| # Depending upon your findings, choose an appropriate workflow action:
| |
| #* ''Pass'' - Test runs perfectly :-)
| |
| #* ''Fail'' - Indicate in a comment where the test fails and include a MDL issue link to the report of the problem ([http://tracker.moodle.org/secure/CreateIssue!default.jspa creating a new issue] if necessary)
| |
| #* ''Obsolete'' - Test is no longer relevant in the current Moodle version (unlikely for Moodle 2.0, but may occur when testing Moodle 2.1)
| |
| | |
| ==Writing new tests==
| |
| | |
| Currently the list of tests [http://tracker.moodle.org/browse/MDLQA MDLQA] is incomplete. If you would like to help writing new QA tests, please contact [http://moodle.org/user/view.php?id=24152&course=1 Helen] in order to be given appropriate tracker permissions.
| |
| | |
| Each test should state a task that can be done in Moodle. The test should be feature sized (i.e. not too small and not too large). Something that could be explained to a user in 3 to 10 steps. Most settings should be mentioned. For example:
| |
| | |
| GOOD: Users can post replies to forum posts, including embedded media and attached documents.
| |
| BAD: Users can have discussions.
| |
| BAD: Users can click a button named "Reply".
| |
| | |
| ==Component leads==
| |
| | |
| If you would like to take responsibility for testing a particular area of Moodle, for example the lesson module, please contact [http://moodle.org/user/view.php?id=24152&course=1 Helen]. You will be named as component lead, resulting in all new tests for your chosen component being automatically assigned to you.
| |
| | |
| ==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.
