MozillaWiki

QA/Automation/Projects/Mozmill Automation: Difference between revisions

Page Discussion

QA/Automation/Projects/Mozmill Automation (view source)

Revision as of 23:02, 30 September 2011

449 bytes removed ,  30 September 2011
Undo revision 353665 by Whimboo (talk)
No edit summary
(Undo revision 353665 by Whimboo (talk))
Line 1: Line 1:
__NOTOC__
=Overview=
 
{|  
==Overview==
  | style="width: 33%" |
Mozilla QA is using the existing Mozmill tests to run automated tests against any kind of Firefox build. While this is reducing the time we have to spent on manual testing, we can also enhance our testing to more than only Firefox BFT tests. We have automated test-runs available for software update tests, l10n tests, add-on tests, and others. Those are getting run on any platform, and also for localized builds of Firefox.
  | style="width: 33%" |
 
{| style="width: 90%; margin: 0 0 1em 1em" |
  | style="width: 20%" |
  | style="width: 80%" |
  |- valign="top"
  |- valign="top"
  | '''Name:'''
  | '''Lead:'''
  | Mozmill Automation
  | [mailto:hskupin@mozilla.com Henrik Skupin]
  |- valign="top"
  |- valign="top"
  | '''Leads:'''
  | '''Co-workers:'''
  | [mailto:hskupin@mozilla.com Henrik Skupin], [mailto:gmealer@mozilla.com Geo Mealer]
  | Al Billings, Anthony Hughes
  |- valign="top"
  |- valign="top"
  | '''Contributors:'''
  | '''Dates:'''
  | Dave Hunt
  | No end date set
  |- valign="top"
  |- valign="top"
  | '''Tracker:'''
  | '''Status:'''
  | https://www.pivotaltracker.com/projects/298905
  | Creating and Enhancing Scripts
  |- valign="top"
  |- valign="top"
  | '''Repository:'''  
| '''Specs:'''
  | http://hg.mozilla.org/qa/mozmill-automation/
| [http://docs.google.com/Doc?docid=0AVroormSQgiRZDljejN3a18xNmNrdmY2a2Rn&hl=en Add-on test-run script]
|- valign="top"
  | '''Repository Location:'''
  | [http://hg.mozilla.org/qa/mozmill-automation/file/tip Automated Test-run Scripts]
  |- valign="top"
  |- valign="top"
  | '''Etherpad:'''
  | '''Tracking Bug:'''
  | http://etherpad.mozilla.com:9000/qas-mozmill-automation
  | {{bug|562639}}
|}
|}
 
=Excerpt=
Mozilla QA is using the existing Mozmill tests to run automated tests against any kind of Firefox build. While this is reducing the time we have to spent on manual testing, we can also enhance our testing to more than only Firefox BFT tests. We plan to have automated test-runs available for software update tests, l10n tests, add-on tests, and others. Those will have to be run on any platform and also against localized builds of Firefox.
 
=Project details=
The way to reach the state when everything is automated is long can can be divided into the following sub-projects:
 
* Setting up a machine which can be used for automated tests
* Creation of scripts which cover all automation aspects
* Running the automation for release builds
 
==Machine for Automated Testing==
A machine in the QA lab is needed at least for the first time. Once we have a stable process we can consider to integrate the automation into the Releng process.
 
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==
The automation scripts should allow us to have a complete automated process in-place. That means that only a trigger would be necessary to start those release tests. The following areas have to be covered:
 
* Script for Downloading builds from the FTP Server ({{bug|528064}})
* Script for Smoketests, BFT, and FFT Test-runs ({{bug|563523}})
* Script for Software Update Test-runs ({{bug|564539}})
* Script for Add-ons Test-run ({{bug|562445}})
* Script for L10n Test-run ({{bug|565196}})
* Script for Accessibility Test-run ({{bug|565201}})


==Goals for Q3/11==
===Downloading builds from the FTP Server===
TBD.
For a complete automation of our Mozmill tests for release testing, a download script is necessary which will fetch all the builds to test from the FTP server and store those locally. The work is being tracked on {{bug|528064}}.


{| class="fullwidth-table" |
===Smoketests, BFT, and FFT Test-run===
| style="background:#EFEFEF; width: 15%" | Status
To execute all existing Mozmill tests which have been written for the Smoketest, BFT, and FFT testgroup of Litmus this script is useful. Once it has been called it should automatically execute the steps below:
| style="background:#EFEFEF; width: 25%" | Task
 
| style="background:#EFEFEF; width: 60%" | Description
* Install a build (if requested)
|- valign="top"
* Run the tests from all those three testgroups
|
* Uninstall the build (if requested)
|
 
  |  
The work is being tracked on {{bug|563523}}.
|}


==Sub Projects==
===Software Update Test-run===
{| class="fullwidth-table" |
To run the software update tests automatically a test-run script is required which will take care of any aspect of the tests to be run. Once it has been called it should automatically execute the steps below:
| style="background:#EFEFEF; width: 25%" | Sub Project
| style="background:#EFEFEF; width: 55%" | Description
|- valign="top"
| [[QA/Automation_Services/Projects/Mozmill_Shared_Modules/|QA/Automation_Services/Projects/Mozmill_Shared_Modules/]]
|
|}


==Details==
* Install a build (if requested)
Whenever you want to start to automate a new BFT/FFT subgroup on Litmus, you should first think about having a shared module in place. Creating a list of requirements should be the first step you will have to do as early as possible in the whole process. That will allow us to help you or even write the shared module on our own. Once it has been done, you can start writing Mozmill tests for that subgroup.
* Create a backup of the build
* Run the partial or complete software update tests
* Restore the backup
* Run the fallback software update tests
* Restore the backup
* Run background software update tests
* Uninstall the build (if requested)


===Identifying Requirements===
A script with this feature set has already been created on {{bug|504653}} and is able to execute all the steps except step 6. The reason is that we do not have any automated tests for background software updates yet.
This part is probably not trivial if you are doing it the first time. That's why we want to offer some help for the requirements definition process. By following the steps below you will be able to put a good list of items together.  


Before you start with the list below, make sure that there hasn't been already made a request. Therefore check the BFT table of the [http://spreadsheets.google.com/ccc?key=pAP5Y5AH3-Tl-wRoNgBujUQ&pli=1 Mozmill spreadsheet] and also all open requests for shared modules. If your request cannot be found, you can start to identify the requirements.
===Add-on Test-run===
The script for the add-ons test-run simplifies the work which would have to be done to run Mozmill tests against available add-ons. Once it has been called it should automatically execute the steps below:


1. Each of the tests will interact with a couple of ui elements. All those elements can be accessed in different ways. The easiest way is definitely its node id. But there are probably more elements which can't be reached by that method and requires a complex lookup expression. As a test writer you don't wanna be confronted with such a research task because it requires knowledge about the DOM and tools like the [https://addons.mozilla.org/de/firefox/addon/6622 DOM inspector]. Instead you want to simply use those elements and create sequential steps of actions. To be able to do that, the shared module has to give access to all elements in the same simple manner by only specifying the elements name and eventually an index. As result the getElement function has been added to all shared modules and has to be used to retrieve elements.
* Install a build (if requested)
* Perform Mozmill tests against any available add-on
** Download the specified version of the add-on
** Start Firefox with the extension installed
** Run all available tests
** Clean-up the system
* Uninstall the build (if requested)


2. Tests from the same subgroup normally have similar actions which have to be performed to get into a given state. Those single steps shouldn't be performed again and again by the tests itself. Instead a function should be created in the shared module which combines those steps in a single call.  
The work is being  tracked on {{bug|562445}}.


3. Sometimes the new shared module can have dependencies to other shared modules. Take the AddonsAPI as an example. It reads and writes some preferences and needs functions from the PrefsAPI.
===L10n Test-run===
With the creation of [[QA/Mozmill_Test_Automation/L10n_Tests|l10n tests]] we will be able to perform specific tests for localizers. Once it has been called it should automatically execute the steps below:


===Filing a Bug===
* Install a build (if requested)
To get the shared module implemented you will have to file a [https://bugzilla.mozilla.org/enter_bug.cgi?component=Mozmill Shared Modules&form_name=enter_bug&op_sys=All&product=Mozilla QA&rep_platform=Al&short_desc=Implement shared module for %25Feature%25 new bug]. Use a clear summary and add the requirements you have compiled in the former chapter.
* Run all the l10n tests
* Uninstall the build (if requested)


===Implementation===
The work is being  tracked on {{bug|565196}}.
The creation of shared modules is not as easy as creating tests, but it's more challenging because you really have to think in an abstract way. If you haven't written a shared module yet, please check our [http://hg.mozilla.org/qa/mozmill-tests/file/default/lib/ existing shared modules]. Those can give you an insight how the code has to look like. You should also obey the [https://developer.mozilla.org/en/Mozmill_Tests#Writing_Mozmill_Tests test writing guidelines].  


While creating the shared module you should immediately check if the functions you have added are working as expected. Therefore you can create tests under [http://hg.mozilla.org/qa/mozmill-tests/file/default/lib/tests lib/tests] with the same name as the shared module or the class itself. The [https://developer.mozilla.org/en/Mozmill_Tests/Shared_Modules#How_to_use_a_Shared_Module shared module documentation] explains how to include the shared module into a test.
===Accessibility Test-run===
With the creation of [[QA/Mozmill_Test_Automation/Accessibility_Tests|accessibility tests]] we will be able to perform specific tests for keyboard navigation. Once it has been called it should automatically execute the steps below:


Before the shared module can be checked-in a review is necessary. Therefore create a patch and ask for review. Details about that process can be found on [https://developer.mozilla.org/en/Mozmill_Tests#The_Review_Process MDC].
* Install a build (if requested)
* Run all the accessibility tests
* Uninstall the build (if requested)


==Resources==
The work is being  tracked on {{bug|565201}}.
* [[/Public|Public Posts and Discussions]]
* [[/Presentations|Presentations]]
* [[/FAQ|FAQ]]
* [[/Contribution|How to Contribute]]
Whimboo
canmove, Confirmed users, Bureaucrats and Sysops emeriti
4,714

edits

Retrieved from "https://wiki.allizom.org/Special:MobileDiff/353666"