Confirmed users
14,525
edits
| Line 104: | Line 104: | ||
|} | |} | ||
''Prioritized by increasing complexity and decreasing need'' | ''Prioritized by increasing complexity and decreasing need'' | ||
=== Test Failures === | |||
The Test Failures project focuses on repairing tests which have started failing. Most of the time this results in a test having to be refactored due to a change in Firefox. Once in a while this ends up being a Firefox regression. It is of utmost importance that we tackles these issues as swiftly as possible. | |||
; How to Help | |||
* Familiarize yourself with some of our existing [http://hg.mozilla.org/qa/mozmill-tests/file/default/tests/functional functional tests] | |||
* Familiarize yourself with the [https://developer.mozilla.org/en/Mozmill_Tests Mozmill Tests documentation] and try running some tests | |||
* Review our [https://docs.google.com/spreadsheet/ccc?key=0AmkRt0ylPb8zdEhjOXRUak1MY1ViaS1zT2hBRWd4QlE&hl=en_US#gid=2 worksheet] and find an UNASSIGNED test you would like to try fixing | |||
* If you can't find something, [http://mozmill-release.brasstacks.mozilla.com/#/functional try checking our dashboard] and see if a new failure has happened which you would like to solve | |||
* Once you've found a test you want to fix, see if you can reproduce it locally (on your machine) | |||
* File a bug and sign onto the #automation channel on IRC to get help | |||
=== Endurance Tests === | === Endurance Tests === | ||