QA/Mozmill Test Automation/Test Writing

From MozillaWiki
< QA‎ | Mozmill Test Automation
Revision as of 13:27, 15 April 2010 by Whimboo (talk | contribs) (Created page with '=Creating Mozmill Tests= Once you have figured out how to run Mozmill tests you will probably have interests in helping us with the creation of new tests. The best way by far is …')
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Creating Mozmill Tests

Once you have figured out how to run Mozmill tests you will probably have interests in helping us with the creation of new tests. The best way by far is to contact Henrik and ask for new test candidates. It will make sure that no-one is working on the same test in parallel.

We are tracking all the ongoing work in the Mozmill spreadsheet on Google. The tests have been split up into the three areas Smoketests, BFTs, and FFTs so far. The current focus is getting the BFT tests especially the ones from the P1 and P2 priority written.

When a test has been assigned to you, a bug has to be filed on Bugzilla. Take bug 536439 as an example and check the following steps:

  • File the bug in the corresponding product/component as given by the Litmus subgroup
  • Use [mozmill] as prefix for the summary
  • Enter references to the Litmus tests for all branches into the comment field

After everything has been setup you can start writing the Mozmill test by following the steps given in the Litmus test and the test writing documentation.

To get the new test checked-in into our mozmill-test repository you will have to create a patch and go through the usual review cycle.