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

QA testing: diferència entre les revisions

De MoodleDocs
Salta a:navegació, cerca
(test lists, writing new tests further info)
Línia 18: Línia 18:
* [[Question tests]]
* [[Question tests]]
* [[Community hub tests]]
* [[Community hub tests]]
* [[Messaging tests]]


''More areas to be added soon...''
''More areas to be added soon...''

Revisió del 11:53, 6 jul 2010

Getting involved

Would you like to help with QA testing? If so, please contact Helen.

All testers are members of the testers group in the Moodle Tracker, enabling them to assign, comment and pass or fail Moodle QA issues.

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.

  1. Browse the test lists (see links below) and choose some tests you'd like to run
  2. For each chosen test, find the operation "Assign this issue" in the left column and click the "to me" link

Test lists

More areas to be added soon...

Running tests

  1. Using either the 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
  2. Optional: Add a comment on your findings
  3. 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 (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 MDLQA is incomplete. If you would like to help writing new QA tests, please contact 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".

Tests should be listed on a page in Moodle Docs. To add a new test, click the create a sub-task link in MDLQA-1.

Component leads

If you would like to take responsibility for testing a particular area of Moodle, for example the lesson module, please contact 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 Testing and QA forum in Using Moodle.