QA/Desktop Firefox/Automation: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 131: Line 131:
</pre>
</pre>
* Add Litmus test to ''Aurora Mozmill Tests'' subgroup
* Add Litmus test to ''Aurora Mozmill Tests'' subgroup
=== l10n Tests ===
; What Are They?
l10n Tests are used to verify the numerous language translations (locales) do not break functionality and UI in Firefox.
; Important Links
{| class="querytable"
|-
| class="header" | Link
| class="header" | Summary
|-
| {{bug|562084}}
| Root bug for tracking all current development work
|-
| [https://litmus.mozilla.org/show_test.cgi?searchType=by_category&product_id=1&branch_id=44&testgroup_id=271&subgroup_id= Aurora l10n Testgroup]
| These are the manual tests we are trying to automate
|-
| [https://docs.google.com/spreadsheet/ccc?key=0AmkRt0ylPb8zdEhjOXRUak1MY1ViaS1zT2hBRWd4QlE&hl=en_US#gid=9 Worksheet]
| Tracks coverage of automated tests -- use this to find something to work on
|-
| [http://hg.mozilla.org/qa/mozmill-tests/file/default/ hg.mozilla.org]
| The source code repository for [http://hg.mozilla.org/qa/mozmill-tests/file/default/tests/l10n tests] and [http://hg.mozilla.org/qa/mozmill-tests/file/default/lib shared modules]
|-
| [http://mozmill-release.brasstacks.mozilla.com/#/l10n/reports brasstacks]
| Dashboard of results from the l10n testruns
|}
; How to Start?
* Familiarize yourself with some existing code
* Find a test you want to automate (use the worksheet above)
* File a bug:
** instructions for bug...
* Start coding
; What to do when RESOLVED FIXED?
* Wait until the next day's testrun to appear on the dashboard, and verify that your test passes
* Assuming it passes, update the worksheet
* Add the following boilerplate to the Litmus test
<pre>
<hr />
Covered by Mozmill test:<br>
<a href="URL TO TEST IN default BRANCH ON hg.mozilla.org">folder/testModule.js</a>
</pre>
* Add the Litmus test to ''Aurora Mozmill Tests'' subgroup
* ''should you be unable to perform any of the above duties, please comment in your bug''


= Getting Started =
= Getting Started =

Revision as of 06:23, 30 November 2011

UNDER CONSTRUCTION

This is being refactored from the old documentation here


If you are looking for the Automation Services team, please go to their team page.

Overview

Mozilla QA uses Mozmill, a tool developed for test automation of applications based on the Gecko Platform (XUL Runner).

We use this tool to automate our manual tests in Litmus. The primary goal is to lessen the time we spend actively testing Smoketest, Basic Functional, and Full Functional level regression tests; enabling us to focus our time more on deep testing of bleeding-edge features and bugs.

An added benefit of using automation is that we can run tests across multiple platforms and locales in parallel, thereby increasing the coverage of regression tests in a smaller amount of time. To put that all into perspective, a single person running the BFTs on one platform and one locale takes about 8 hours. Mozmill can run the same tests across all platforms and all locales in a couple of hours.

The Mozmill tool and APIs are maintained and developed by the Automation Services team. The relatively small Desktop Automation team is responsible for developing the tests. This is where we need you, the community.

The Team

Person Photo Location Role
Anthony Hughes
IRC: ashughes
Vancouver, Canada Team Lead
Vlad Maniac
IRC: vladmaniac
Cluj, Romania Contractor Lead
Alex Lakatos
IRC: AlexLakatos
Cluj, Romania Developer
Remus Pop
IRC: remuspop
Cluj, Romania Developer

You can get in contact with us in a few different ways:

  • Take part in a discussion on the mozmill-dev mailing list
  • Join the #mozmill IRC channel to ask about Mozmill
  • Join the #automation IRC channel to ask about test automation

Meetings

Every two weeks we meet to discuss the progress we have made, where we want to go, and how we are going to get there. You can learn a lot about what we do just by listening in to one of our meetings. These meetings are open to everyone.

Meeting Information:

   When: Mondays, 8am PT / 4pm GMT
Dial-in: +1 (800) 707-2533 Password 369 Conference 654

Areas of Work

Projects

Project Summary Priority Status % COMPLETE Documents
Failures Repair broken tests P1 6 / 17 33.3 % worksheet
Endurance Tests measuring resource usage in various scenarios P2 6 / 27 23.1 % worksheet
Smoketests Tests covering the most basic functionality P3 15 / 32 45.5 % worksheet
Restart Tests requiring Firefox to restart P4 19 / 29 65.5 % worksheet
Functional Tests covering more advanced functionality P5 75 / 122 61.5 % worksheet
l10n Tests for the numerous localizations/languages P7 2 / 2 100 % worksheet

Prioritized by increasing complexity and decreasing need

How To Help

Test Failures

RESOLVED FIXED
  • Verify test passes using the next day's dashboard results
  • Update the spreadsheet
  • Re-enable the test in Litmus

New Tests

RESOLVED FIXED
  • Verify test passes using next day's dashboard results
  • Update spreadsheet
  • Add boilerplate to Litmus test
<hr />
Covered by Mozmill test:<br>
<a href="URL TO TEST IN default BRANCH ON hg.mozilla.org">folder/testModule.js</a>
  • Add Litmus test to Aurora Mozmill Tests subgroup

l10n Tests

What Are They?

l10n Tests are used to verify the numerous language translations (locales) do not break functionality and UI in Firefox.

Important Links
Link Summary
bug 562084 Root bug for tracking all current development work
Aurora l10n Testgroup These are the manual tests we are trying to automate
Worksheet Tracks coverage of automated tests -- use this to find something to work on
hg.mozilla.org The source code repository for tests and shared modules
brasstacks Dashboard of results from the l10n testruns
How to Start?
  • Familiarize yourself with some existing code
  • Find a test you want to automate (use the worksheet above)
  • File a bug:
    • instructions for bug...
  • Start coding
What to do when RESOLVED FIXED?
  • Wait until the next day's testrun to appear on the dashboard, and verify that your test passes
  • Assuming it passes, update the worksheet
  • Add the following boilerplate to the Litmus test
<hr />
Covered by Mozmill test:<br>
<a href="URL TO TEST IN default BRANCH ON hg.mozilla.org">folder/testModule.js</a>
  • Add the Litmus test to Aurora Mozmill Tests subgroup
  • should you be unable to perform any of the above duties, please comment in your bug

Getting Started

To help you get started, we have put together a couple of guides:

Of course, if you have any questions, you can always reach us by: