canmove, Confirmed users, Bureaucrats and Sysops emeriti
4,747
edits
| Line 29: | Line 29: | ||
=Project Details= | =Project Details= | ||
In general there are about 700 manual tests on Litmus which could be automated. Those tests are separated into three different groups: Smoketests, BFT (Basic Functional Tests), and FFT (Full Functional Tests). While seeing that amount of tests are focus is currently on Smoketests and BFT tests. The reason therefore is that those tests have to be run for every security release of Firefox and need attention from QA. Having those automated would give us the chance to set the focus of manual testing to areas where check-ins happened for the new release. All other tests could be run automatically. | |||
Once we have nearly finished the BFT testgroup, we will have to check if automating all FFT's is useful or not. | |||
Once | |||
==Identifying a Test Candidate== | |||
Once you have learned how to [https://developer.mozilla.org/en/Mozmill_Tests#Running_Mozmill_Tests run Mozmill tests], you will probably have interests in creating a test yourself. The first step would be to check which tests already have been automated, which are in the works and which are remaining. | |||
To track the ongoing work we have created a [http://spreadsheets.google.com/ccc?key=pAP5Y5AH3-Tl-wRoNgBujUQ&pli=1 Google spreadsheet]. The different tables show the status of the above mentioned testgroups. Checkout the BFT table to scan available subgroups which have to be automated. If you are interested in a subgroup check if there is already an owner set. Get in contact with him or send an email to Henrik, who can coordinate the work. We can figure out the necessary requirements which have to be fulfilled before work can start on this subgroup. If nothing has been done so far it's highly recommended to create a [[QA/Mozmill_Test_Automation/Shared_Modules|Shared Module]] as the first step before any test can be implemented. | |||
==Filing a Bug== | ==Filing a Bug== | ||