canmove, Confirmed users, Bureaucrats and Sysops emeriti
4,714
edits
QA/Automation/Projects/Crowd Testing/Documentation: Difference between revisions
QA/Automation/Projects/Crowd Testing/Documentation (view source)
Revision as of 21:19, 26 January 2011
, 26 January 2011no edit summary
(→TBD) |
No edit summary |
||
| Line 7: | Line 7: | ||
=Objective= | =Objective= | ||
* Empower users of Firefox to run all of our automated functional Mozmill tests | * Empower users of Firefox to run all of our automated functional Mozmill tests | ||
* Make the setup of the | * Make the setup of the Mozmill test environment transparent to the user | ||
* Collect test results across all supported locales and geographical locations | * Collect test results across all supported locales and geographical locations | ||
=Product Components= | =Product Components= | ||
==The Storage Folder== | |||
TBD | |||
==The Test Environment== | |||
Before Mozmill tests can be run on a machine, the test environment has to be installed first. It includes all necessary tools and modules which are necessary to run Mozmill and to execute our automation scripts. | |||
Due to any operating system brings its own set of pre-installed software, the test environment will be different for each one. See the tables below which tools and modules the environments contain. The environment will be a part of the storage folder. | |||
For the installation of additional Python modules a virtual environment is used. That ensures that we do not change any configuration of the users system and stay local in our sandbox. All the modules will be installed during the setup of the test environment. Update checks will happen in the background each time the Mozmill Crowd dialog gets opened by the user. | |||