QA/Desktop Firefox/Automation: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 121: Line 121:
* Familiarize yourself with some of our existing [http://hg.mozilla.org/qa/mozmill-tests/file/default/tests/functional functional tests]
* Familiarize yourself with some of our existing [http://hg.mozilla.org/qa/mozmill-tests/file/default/tests/functional functional tests]
* Familiarize yourself with the [https://developer.mozilla.org/en/Mozmill_Tests Mozmill Tests documentation] and try running some tests
* Familiarize yourself with the [https://developer.mozilla.org/en/Mozmill_Tests Mozmill Tests documentation] and try running some tests
* Review our [https://docs.google.com/spreadsheet/ccc?key=0AmkRt0ylPb8zdEhjOXRUak1MY1ViaS1zT2hBRWd4QlE&hl=en_US#gid=2 worksheet] and find an UNASSIGNED test you would like to try fixing
* Review the list of open and unassigned [http://bit.ly/wByTFy test failure bugs]
* If you can't find something, [http://mozmill-release.brasstacks.mozilla.com/#/functional try checking our dashboard] and see if a new failure has happened which you would like to solve
* Sign onto the #automation channel on IRC to get help or [mailto:ahughes@mozilla.com send an email] to Anthony Hughes
* Once you've found a test you want to fix, see if you can reproduce it locally (on your machine)
* File a bug and sign onto the #automation channel on IRC to get help


; Policy for handling Failures
; Policy for handling Failures

Revision as of 21:02, 2 March 2012

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 Location Role
Anthony Hughes
IRC: ashughes 		Vancouver, Canada Team Lead
Vlad Maniac
IRC: vladmaniac 		Cluj, Romania Developer 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

Weekly Status

Weekly Project Status

Every week we maintain an archive of the work accomplished and discussion had. Please select a link below to see that week's status page.

Areas of Work

Projects

Project Summary Bugs Availability
Good First Bug Hand-picked bugs ideal for a launching point into test development good first bug 3 Bugs Available
Failures Repair broken tests [mozmill-test-failure] worksheet
Endurance Tests measuring resource usage in various scenarios [mozmill-endurance] worksheet
Smoketests Tests covering the most basic functionality [mozmill-smoketest] worksheet
Restart Tests requiring Firefox to restart [mozmill-restart] worksheet
Functional Tests covering more advanced functionality [mozmill-functional] worksheet
l10n Tests for the numerous localizations/languages [mozmill-l10n] worksheet
Add-ons Tests for Firefox add-ons worksheet
Local Data Creating local data for all of our remote test cases
Test Refactoring Refactoring existing tests to use new APIs mozmill-test-refactor 5 Bugs Available

Prioritized by increasing complexity and decreasing need

Test Failures

The Test Failures project focuses on repairing tests which have started failing. Most of the time this results in a test having to be refactored due to a change in Firefox. Once in a while this ends up being a Firefox regression. It is of utmost importance that we tackles these issues as swiftly as possible.

How to Help
Policy for handling Failures
  • Any failures which only affect the mozilla-1.9.2 branch will be disabled, the bug resolved WONTFIX
  • Otherwise, follow this process:
    • Disable the test
    • Investigate if the bug is a failure of the test or Firefox
    • If it's a problem with the test, the test will remain disabled until it can be fixed
    • If it's a problem with Firefox, file a Firefox bug, re-enable the test and close the test failure bug

Endurance Tests

The Endurance Tests project focuses on development of automated tests which try to expose performance regressions in Firefox. Currently, they only measure memory usage but there are future plans to expand this out to CPU and I/O usage.

How to Help

Smoketests

The Smokestests project focuses on development of automated tests for the manual smoketests run with every release. The aim here is to lessen the time spent running manual smoketests, devoting it to more important areas of release testing.

How to Help
  • Familiarize yourself with some of our existing functional tests
  • Familiarize yourself with the Mozmill Tests documentation and try running some of the tests
  • Check out our Functional Dashboard to see some recent results
  • Review our worksheet and find an UNASSIGNED test you would like to try automating
  • File a bug and sign onto the #automation channel on IRC to get help

Restart Tests

The Restart Tests project focuses on development of automated tests requiring a restart of the browser (Add-on installation for example). They are very similar to Smoketests except that each test is broken into a separate file (book-ended by restarts). One of the unique benefits of Mozmill is that it can persist across the restart of a browser and therefor test in ways other frameworks cannot.

How to Help

Functional Tests

more to come soon...

l10n Tests

The l10n Tests project focuses on development of automated tests for the numerous language translations (locales). The majority of these tests are UI focused, checking to make sure the localized strings do not break the look and feel of Firefox.

How to Help
  • Familiarize yourself with some of our existing l10n tests and Litmus tests
  • Familiarize yourself with the Mozmill Tests documentation and try running some of the tests
  • Check out our L10n Dashboard to see some recent results
  • Review our worksheet and find an UNASSIGNED test you would like to try automating
  • File a bug and sign onto the #automation channel on IRC to get help

Add-ons Tests

More to come soon...

dashboard

Good First Bug

The good-first-bug project is all about getting your feet wet with Mozmill Tests development. These bugs are hand-picked from all other projects. They are ideal candidates for your first attempt at writing a patch and fixing a bug for Mozilla.

Test Refactoring

The Test Refactoring project is about refactoring (changing) the code in existing tests to use current APIs. The Mozmill APIs undergo changes frequently to make tests easier to write, implement new features, or to stabilize the test suite. Some of the tests are well over a year old and need to be updated to these new improvements. This is a great way to learn the structure of tests, the APIs and how they are used.

Contributing

Before you Begin

Getting Started

  • Set up your Mozmill development environment (if you have not done so already)
  • Pick an project which fits best with your area of interest
  • Familiarize yourself with some existing code
  • Pick a project which interests you
  • Assign a bug to yourself or file a new one
  • Start coding
  • Submit your first patch into the review process
  • Remember to ask for help via email or on irc.mozilla.org #automation

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="http://hg.mozilla.org/qa/mozmill-tests/file/default/tests/testFolder/testModule.js">
  testFolder/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

Where to get Help

Commit Policy

Check out our commit policy on MDN

Retrieved from "https://wiki.mozilla.org/index.php?title=QA/Desktop_Firefox/Automation&oldid=403448"