canmove, Confirmed users, Bureaucrats and Sysops emeriti
4,747
edits
QA/Mozmill Test Automation/Test Writing: Difference between revisions
Jump to navigation
Jump to search
QA/Mozmill Test Automation/Test Writing (view source)
Revision as of 14:43, 17 April 2010
, 17 April 2010→Project Details
| Line 39: | Line 39: | ||
==Filing a Bug== | ==Filing a Bug== | ||
After a test has been assigned to you, a bug has to be filed on Bugzilla. We have prepared a [https://bugzilla.mozilla.org/enter_bug.cgi?alias=&assigned_to=nobody%40mozilla.org&cc=hskupin%40gmail.com&component=Mozmill&form_name=enter_bug&keywords=&product=Testing&qa_contact=mozmill%40testing.bugs&rep_platform=All&short_desc=[mozmill]%20Implement%20test%20for%20[Litmus%20test%20summary]&comment=This%20bug%20covers%20the%20following%20Litmus%20tests:%0D%0Ahttps://litmus.mozilla.org/show_test.cgi?id=id template] which makes the creation as easy as possible. | After a test has been assigned to you, a bug has to be filed on Bugzilla. We have prepared a [https://bugzilla.mozilla.org/enter_bug.cgi?alias=&assigned_to=nobody%40mozilla.org&cc=hskupin%40gmail.com&component=Mozmill&form_name=enter_bug&keywords=&product=Testing&qa_contact=mozmill%40testing.bugs&rep_platform=All&short_desc=[mozmill]%20Implement%20test%20for%20[Litmus%20test%20summary]&comment=This%20bug%20covers%20the%20following%20Litmus%20tests:%0D%0Ahttps://litmus.mozilla.org/show_test.cgi?id=id template] which makes the creation as easy as possible. | ||
Just obey the following steps: | |||
* Add the description of the Litmus test to the summary | * Add the description of the Litmus test to the summary | ||
* Enter references to Litmus tests for all branches (3.7, 3.6, and 3.5) into the comment field | * Enter references to Litmus tests for all branches (3.7, 3.6, and 3.5) into the comment field | ||
| Line 54: | Line 55: | ||
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]. | ||
==Verification== | |||
Once the patch has been checked-in, the bug will be marked as fixed. We will wait for the next test-run on our machine in the QA lab. 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. | |||