canmove, Confirmed users, Bureaucrats and Sysops emeriti
4,747
edits
QA/Mozmill Test Automation/Test Writing: Difference between revisions
QA/Mozmill Test Automation/Test Writing (view source)
Revision as of 03:52, 12 November 2010
, 12 November 2010no edit summary
No edit summary |
|||
| Line 56: | Line 56: | ||
To get the new test checked-in into our [http://hg.mozilla.org/qa/mozmill-tests/ mozmill-test repository] you will have to create a patch and go through the usual [https://developer.mozilla.org/en/Mozmill_Tests#Review_Process review cycle]. | To get the new test checked-in into our [http://hg.mozilla.org/qa/mozmill-tests/ mozmill-test repository] you will have to create a patch and go through the usual [https://developer.mozilla.org/en/Mozmill_Tests#Review_Process review cycle]. | ||
== | == Finishing up the test == | ||
Before the bug can be marked as fixed, the corresponding Litmus tests have to be updated. Please make sure that the tests for all the supported branches are getting updated. There are two steps necessary: | Before the bug can be marked as fixed, the corresponding Litmus tests have to be updated. Please make sure that the tests for all the supported branches are getting updated. There are two steps necessary: | ||
1. Use the following template and add the content at the bottom of the steps to execute. Make sure to correctly specify the branch after the 'file' fragment: | 1. Use the following template and add the content at the bottom of the steps to execute. Make sure to correctly specify the branch after the 'file' fragment: | ||
<blockquote><br/><hr/><br>This test is covered by Mozmill: [testCookies/testRemoveCookie.js](http://hg.mozilla.org/qa/mozmill-tests/file/default/firefox/testCookies/testRemoveCookie.js) </blockquote> | |||
2. Add the test to the 'Mozmill Tests' / 'Mozmill - All' testgroup. | |||
Also take care of the Mozmill test coverage spreadsheet and add a line with the litmus id's to the data table. | |||
Also take care of the Mozmill test coverage spreadsheet and add a line with the litmus id's to the data table. | |||
Once this has been done, the bug can be marked as fixed. Wait for the next test-run on the QA machine. If no problems or regressions appear we are fine and you did a great job. Otherwise we have to back-out the patch and go back to the investigation phase and check why the test fails. | Once this has been done, the bug can be marked as fixed. Wait for the next test-run on the QA machine. If no problems or regressions appear we are fine and you did a great job. Otherwise we have to back-out the patch and go back to the investigation phase and check why the test fails. | ||