canmove, Confirmed users, Bureaucrats and Sysops emeriti
4,747
edits
QA/Automation/Projects/Mozmill Automation: Difference between revisions
QA/Automation/Projects/Mozmill Automation (view source)
Revision as of 13:06, 1 June 2010
, 1 June 2010no edit summary
No edit summary |
No edit summary |
||
| Line 40: | Line 40: | ||
This sub-project has been finished. All requirements can be read on {{bug|537840}} | This sub-project has been finished. All requirements can be read on {{bug|537840}} | ||
==Automation Execution== | |||
Right now Mozilla QA is using the machine in the QA lab to run release tests. All tests have to be triggered manually. We consider to use Hudson in the future to control the complete process. | |||
==Automation Scripts== | ==Automation Scripts== | ||
| Line 45: | Line 48: | ||
* Download script to fetch builds from the FTP server ({{bug|528064}} | * Download script to fetch builds from the FTP server ({{bug|528064}} | ||
* | * Script for Smoketests, BFT, and FFT tests | ||
* | * Script for Software Update Test-runs | ||
* Script for Add-ons Test-run ({{bug|562445}}) | |||
== | ===Script for Add-on Test-runs=== | ||
While you would also be able to run tests against extensions directly with Mozmill itself, you would have to download the extension first and specify it as argument to the Mozmill command line client. Those steps can be simplified and will result in a new test-run script for add-ons. | |||
It will become a Python script which can be used to run tests against all or only a particular extension. Once it has been called it should automatically execute the steps below: | |||
* Perform tests against each listed extension | |||
** Download the latest version from the specified URL | |||
** Start Firefox with the extension installed | |||
** Run all available tests | |||
** Clean-up the system | |||