canmove, Confirmed users, Bureaucrats and Sysops emeriti
4,751
edits
QA/Mozmill Test Automation/Fixing Broken Tests: Difference between revisions
QA/Mozmill Test Automation/Fixing Broken Tests (view source)
Revision as of 09:21, 17 June 2010
, 17 June 2010→Identification of Broken Tests
m (→Filing a Bug) |
|||
| Line 35: | Line 35: | ||
2. Mozilla QA runs daily tests in the Mozilla Lab on all platforms. Test results for all those tests are send to our Brasstacks server. You can search through the results on the [http://brasstacks.mozilla.com/couchdb/mozmill/_design/reports/_list/summary/summary reports page]. | 2. Mozilla QA runs daily tests in the Mozilla Lab on all platforms. Test results for all those tests are send to our Brasstacks server. You can search through the results on the [http://brasstacks.mozilla.com/couchdb/mozmill/_design/reports/_list/summary/summary reports page]. | ||
3. Until a web dashboard will be available which will display all the correlations we track the results in the [https://spreadsheets.google.com/ccc?key=0AmkRt0ylPb8zdGpCMFB1bkU1SHp6eGh4Nkd3RzVKWEE&hl=en#gid=1 Mozmill Failures] spreadsheet. | |||
If a test fails constantly make sure to run the same test again with the '--show-errors' option of the Mozmill CLI. The reported error message should be used in the bug report for a clear failure description. | If a test fails constantly make sure to run the same test again with the '--show-errors' option of the Mozmill CLI. The reported error message should be used in the bug report for a clear failure description. | ||