QA/Desktop Firefox/Automation: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
 
(33 intermediate revisions by 7 users not shown)
Line 1: Line 1:
= UNDER CONSTRUCTION =
''This is being refactored from the old documentation [https://wiki.mozilla.org/QA/Mozmill_Test_Automation here]''
''If you are looking for the Automation Services team, please go to their [[QA/Automation_Services|team page]].''
''If you are looking for the Automation Services team, please go to their [[QA/Automation_Services|team page]].''


Line 33: Line 29:
  | Developer
  | Developer
  |-
  |-
  | Remus Pop <br> IRC: remuspop
  | Andreea Matei <br> IRC: AndreeaMatei
  | Cluj, Romania
  | Cluj, Romania
  | Developer
  | Developer
Line 42: Line 38:
* Join the [http://www.mibbit.com/chat/?server=irc.mozilla.org&channel=%23mozmill #mozmill] IRC channel to ask about Mozmill
* Join the [http://www.mibbit.com/chat/?server=irc.mozilla.org&channel=%23mozmill #mozmill] IRC channel to ask about Mozmill
* Join the [http://www.mibbit.com/chat/?server=irc.mozilla.org&channel=%23automation #automation] IRC channel to ask about test automation
* Join the [http://www.mibbit.com/chat/?server=irc.mozilla.org&channel=%23automation #automation] IRC channel to ask about test automation
= Weekly Status =
* [[QA/Desktop_Firefox/Automation/Status:2012-02-24 | 2012-02-24]]
* [[QA/Desktop_Firefox/Automation/Status:2012-02-17 | 2012-02-17]]
* [[QA/Desktop_Firefox/Automation/Meetings:2012-01-09 | 2012-01-09]]
* [[QA/Desktop_Firefox/Automation/Meetings:2011-12-12 | 2011-12-12]]


= Weekly Project 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.
The following is an archive of our weekly accomplishments and discussions.


* '''March 2012''': [[QA/Desktop_Firefox/Automation/Status:2012-03-02 | 2nd]], [[QA/Desktop_Firefox/Automation/Status:2012-03-09 | 9th]]
* '''February 2012''': [[QA/Desktop_Firefox/Automation/Status:2012-02-03 | 3rd]], [[QA/Desktop_Firefox/Automation/Status:2012-02-10 | 10th]], [[QA/Desktop_Firefox/Automation/Status:2012-02-17 | 17th]], [[QA/Desktop_Firefox/Automation/Status:2012-02-24 | 24th]]
* '''February 2012''': [[QA/Desktop_Firefox/Automation/Status:2012-02-03 | 3rd]], [[QA/Desktop_Firefox/Automation/Status:2012-02-10 | 10th]], [[QA/Desktop_Firefox/Automation/Status:2012-02-17 | 17th]], [[QA/Desktop_Firefox/Automation/Status:2012-02-24 | 24th]]


= Areas of Work =
= How You Can Help =
== Projects ==
There are numerous ways you can help us with Mozmill test automation.
{| class="querytable"
|-
| class="header" | Project
| class="header" | Summary
| class="header" | Bugs
| class="header" | Available
|-
| [[#Good_First_Bug | Good First Bug]]
| Hand-picked bugs ideal for a launching point into test development
| [http://bit.ly/szrMtZ good first bug]
| 3 Bugs Available
|-
| [[#Test_Failures | Failures]]
| Repair broken tests
| [https://bugzilla.mozilla.org/buglist.cgi?status_whiteboard_type=allwordssubstr&query_format=advanced&status_whiteboard=mozmill-test-failure [mozmill-test-failure]]
| [http://bit.ly/wByTFy UNASSIGNED]
|-
| [[#Endurance_Tests | Endurance]]
| Tests measuring resource usage in various scenarios
| [https://bugzilla.mozilla.org/buglist.cgi?status_whiteboard_type=allwordssubstr&query_format=advanced&status_whiteboard=mozmill-endurance [mozmill-endurance]]
| [http://bit.ly/yJq6VH UNASSIGNED]
|-
| [[#Smoketests | Smoketests]]
| Tests covering the most basic functionality
| [https://bugzilla.mozilla.org/buglist.cgi?status_whiteboard_type=allwordssubstr&query_format=advanced&status_whiteboard=mozmill-smoketest [mozmill-smoketest]]
| [https://docs.google.com/spreadsheet/ccc?key=0AmkRt0ylPb8zdEhjOXRUak1MY1ViaS1zT2hBRWd4QlE&hl=en_US#gid=0 worksheet]
|-
| [[#Restart_Tests | Restart]]
| Tests requiring Firefox to restart
| [https://bugzilla.mozilla.org/buglist.cgi?status_whiteboard_type=allwordssubstr&query_format=advanced&status_whiteboard=mozmill-restart [mozmill-restart]]
| [https://docs.google.com/spreadsheet/ccc?key=0AmkRt0ylPb8zdEhjOXRUak1MY1ViaS1zT2hBRWd4QlE&hl=en_US#gid=8 worksheet]
|-
| Functional
| Tests covering more advanced functionality
| [https://bugzilla.mozilla.org/buglist.cgi?status_whiteboard_type=allwordssubstr&query_format=advanced&status_whiteboard=mozmill-functional [mozmill-functional]]
| [https://docs.google.com/spreadsheet/ccc?key=0AmkRt0ylPb8zdEhjOXRUak1MY1ViaS1zT2hBRWd4QlE&hl=en_US#gid=7 worksheet]
|-
| [[#l10n_Tests | l10n]]
| Tests for the numerous localizations/languages
| [https://bugzilla.mozilla.org/buglist.cgi?status_whiteboard_type=allwordssubstr&query_format=advanced&status_whiteboard=mozmill-l10n [mozmill-l10n]]
| [https://docs.google.com/spreadsheet/ccc?key=0AmkRt0ylPb8zdEhjOXRUak1MY1ViaS1zT2hBRWd4QlE&hl=en_US#gid=9 worksheet]
|-
| [[#Add-ons_Tests | Add-ons]]
| Tests for Firefox add-ons
|
| [https://docs.google.com/spreadsheet/ccc?key=0AmkRt0ylPb8zdEhjOXRUak1MY1ViaS1zT2hBRWd4QlE&hl=en_US#gid=10 worksheet]
|-
| Local Data
| Creating local data for all of our remote test cases
|
|
|-
| [[#Test_Refactoring | Test Refactoring]]
| Refactoring existing tests to use new APIs
| [http://bit.ly/t5HWZM mozmill-test-refactor]
| 5 Bugs Available
|}
''Prioritized by increasing complexity and decreasing need''


=== How to Help ===
=== Running the Tests ===
There are numerous ways you can help us with Mozmill test automation, listed below in order of simplest to most complex.
By far, the easiest way you can help us is by running the tests using the [https://addons.mozilla.org/en-US/firefox/addon/mozmill-crowd/ Mozmill Crowd] extension. Results can be seen [http://mozmill-crowd.blargon7.com here]. If you notice any failures, report them by [http://bit.ly/wHfgTC filing a bug].
# Run the tests using the Mozmill Crowd extension, results can be seen [http://mozmill-crowd.blargon7.com here]
# Fixing one of our ''good-first-bug'' bugs
# Fixing one of our ''test failure'' bugs
# Create a new ''Endurance'' test
# Create a new ''Functional'' test


; Getting Started
=== Getting Started with Development ===
* 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 the list of open and unassigned bugs from one of the projects above, try to find something you want to work on
* Review the list of open and unassigned bugs from one of the projects below, try to find something you want to work on
* Sign onto the #automation channel on IRC to get help or [mailto:ahughes@mozilla.com send an email] to Anthony Hughes
* Sign onto the #automation channel on IRC to get help or [mailto:ahughes@mozilla.com send an email] to Anthony Hughes
* Be sure to review our [https://developer.mozilla.org/en/Mozmill_Tests#Writing_Mozmill_tests development process] and [https://developer.mozilla.org/en/Mozmill_Tests/Commit_Policy commit policy] so you know what to expect, and what we expect of you
''Everyone on the automation team is willing and able to both help you get started and teach you the skills necessary to be successful. If you aren't sure where to get started or fear you don't have the skills to help, '''just ask!'''''
''Everyone on the automation team is willing and able to both help you get started and teach you the skills necessary to be successful. If you aren't sure where to get started or fear you don't have the skills to help, '''just ask!'''''


; For more details see [[#Contributing | contributing]] below
=== P1 Projects ===
==== Chemspill Regressions ====
The following is the life-cycle for a chemspill regression test.
# MozTrap smoketest is created, in-moztrap+ added to the bug in bugzilla
# Automate the MozTrap smoketest
# Remove the MozTrap smoketest from active testruns, in-qa-automation+ added to the bug in bugzilla


=== Test Failures ===
Firefox 13.0.1:
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.
* {{drop|}} {{bug|756850}} Some combinations of Hebrew vowels and consonants not displayed in certain fonts with harfbuzz
** Out of scope for Mozmill, will be covered through in-testsuite automation
* {{drop|}} {{bug|736731}} Hotmail no longer auto-updates
** Out of scope for Mozmill due to live-site requirements, will be included in manual spotchecks


; Policy for handling Failures
==== MozTrap Smoketests ====
* Any failures which only affect the ''mozilla-1.9.2'' branch will be disabled, the bug resolved WONTFIX
; Not Doable
* Otherwise, follow this process:
The following tests are not possible to automate due to technical dependencies and scope.
** Disable the test
* [https://moztrap.mozilla.org/manage/case/328/ Download and view a PDF] (we could automate once the internal PDF viewer is enabled by default)
** Investigate if the bug is a failure of the test or Firefox
* [https://moztrap.mozilla.org/manage/case/325/ Breakpad end-to-end test] (probably only needs Mozmill 2.0 with crash detection)
** If it's a problem with the test, the test will remain disabled until it can be fixed
* [https://moztrap.mozilla.org/manage/case/334/ Printing common file formats]
** If it's a problem with Firefox, file a Firefox bug, re-enable the test and close the test failure bug
* Downloading and opening common file formats
** [https://moztrap.mozilla.org/manage/case/330/ DMG]
** [https://moztrap.mozilla.org/manage/case/331/ TAR]
** [https://moztrap.mozilla.org/manage/case/332/ EXE]
* Uninstalling Firefox
** [https://moztrap.mozilla.org/manage/case/324/ Linux]
** [https://moztrap.mozilla.org/manage/case/323/ Mac]
** [https://moztrap.mozilla.org/manage/case/321/ Win XP]
** [https://moztrap.mozilla.org/manage/case/322/ Win Vista, 7, 8]
* [https://moztrap.mozilla.org/manage/case/278/ Mozilla maintenance service]
* [https://moztrap.mozilla.org/manage/case/318/ Mac OSX code-sign verification]
* [https://moztrap.mozilla.org/manage/case/260/ Default installation and start Firefox]


=== Endurance Tests ===
; Doable
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.
The following tests are possible to automate and are either assigned or available for anyone to assign to themselves.


=== Smoketests ===
* '''[ASSIGNED]''' [https://moztrap.mozilla.org/manage/case/266/ Video playback of popular formats] ({{bug|489474}})
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.
* '''[FIXED]''' [https://moztrap.mozilla.org/manage/case/327/ Switch-to-Tab in the Awesomebar] ({{bug|779127}})
* '''[ASSIGNED]''' [https://moztrap.mozilla.org/manage/case/329/ Share your geo location] ({{bug|758187}})
* '''[FIXED]''' [https://moztrap.mozilla.org/manage/case/333/ Quit Firefox] ({{bug|757916}}


=== Restart Tests ===
==== Firefox Features ====
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.
* [https://moztrap.mozilla.org/manage/cases/?filter-suite=31 Silent Updates]
* [https://moztrap.mozilla.org/manage/cases/?filter-suite=33 Show in-line PDF]
* [https://moztrap.mozilla.org/manage/cases/?filter-suite=46 In-content Preferences]


=== Functional Tests ===
=== P2 Projects ===
more to come soon...
{|class="querytable"
 
|class="header" style="width:20%" | Project
=== l10n Tests ===
|class="header" style="width:60%" | Description
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.
|class="header" style="width:20%" | Open Bugs
 
|-
=== Add-ons Tests ===
| '''Test Failures'''
More to come soon...
| Fixing tests which have caused a failure and investigating for possible Firefox bugs
 
| [http://bit.ly/wByTFy mozmill-test-failure]
=== 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'''
 
| Updating tests so that they conform to new coding guidelines and modules
=== Test Refactoring ===
| [http://bit.ly/t5HWZM mozmill-test-refactor]
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.
|-
| '''Good First Bug'''
| Bugs which have been hand-picked for new contributors
| [http://bit.ly/szrMtZ good-first-bug]
|-
| '''Local Data'''
| Writing minimized test cases to be used by the tests (web pages, add-ons, etc)
| [http://bit.ly/x8zbLG mozmill-test-data]
|-
| '''Endurance Tests'''
| Writing tests which repeat the same task to stress memory usage
| [http://bit.ly/yJq6VH mozmill-endurance]
|-
| '''Smoketests'''
| Writing tests for the most basic functionality
| [http://bit.ly/zGnG31 mozmill-smoketest]
|-
| '''Functional Tests'''
| Writing tests for more detailed functionality
| [http://bit.ly/yTP5ri mozmill-functional]
|-
| '''l10n Tests'''
| Writing tests to verify compatibility with the numerous languages supported by Firefox
| [http://bit.ly/xogyOF mozmill-l10n]
|-
| '''Restart Tests'''
| Writing tests which verify functionality requiring restart (updates, add-ons, etc)
| [http://bit.ly/ytXscT mozmill-restart]
|-
| '''Add-ons Tests'''
| Writing tests for specific add-ons (Selenium IDE, Google Toolbar, etc)
| [http://bit.ly/zJxpLS mozmill-addons]
|}


== Contributing ==
== Contributing ==
Line 173: Line 157:
* Learn about [https://developer.mozilla.org/en/Mozmill_Tests#Running_Mozmill_tests running tests]
* Learn about [https://developer.mozilla.org/en/Mozmill_Tests#Running_Mozmill_tests running tests]
* Learn about [https://developer.mozilla.org/en/Mozmill_Tests#Writing_Mozmill_tests writing tests]
* Learn about [https://developer.mozilla.org/en/Mozmill_Tests#Writing_Mozmill_tests writing tests]
* Learn about our [https://developer.mozilla.org/en/Mozmill_Tests/Commit_Policy commit policy]
=== Where to get Help ===
* Joining the [http://www.mibbit.com/chat/?server=irc.mozilla.org&channel=%23automation #automation] channel on IRC and ask for help
* Sending an email directly to [mailto:ahughes@mozilla.com Anthony Hughes]


=== Getting Started ===
=== Getting Started ===
Line 197: Line 186:
* Add the Litmus test to ''Aurora Mozmill Tests'' subgroup
* 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''
* ''should you be unable to perform any of the above duties, please comment in your bug''
=== Where to get Help ===
* Joining the [http://www.mibbit.com/chat/?server=irc.mozilla.org&channel=%23automation #automation] channel on IRC and ask for help
* Sending an email directly to [mailto:ahughes@mozilla.com Anthony Hughes]
== Commit Policy ==
Check out our commit policy on [https://developer.mozilla.org/en/Mozmill_Tests/Commit_Policy MDN]

Latest revision as of 14:08, 18 October 2012

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
Andreea Matei
IRC: AndreeaMatei 		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 Project Status

The following is an archive of our weekly accomplishments and discussions.

How You Can Help

There are numerous ways you can help us with Mozmill test automation.

Running the Tests

By far, the easiest way you can help us is by running the tests using the Mozmill Crowd extension. Results can be seen here. If you notice any failures, report them by filing a bug.

Getting Started with Development

  • Familiarize yourself with some of our existing functional tests
  • Familiarize yourself with the Mozmill Tests documentation and try running some tests
  • Review the list of open and unassigned bugs from one of the projects below, try to find something you want to work on
  • Sign onto the #automation channel on IRC to get help or send an email to Anthony Hughes
  • Be sure to review our development process and commit policy so you know what to expect, and what we expect of you

Everyone on the automation team is willing and able to both help you get started and teach you the skills necessary to be successful. If you aren't sure where to get started or fear you don't have the skills to help, just ask!

P1 Projects

Chemspill Regressions

The following is the life-cycle for a chemspill regression test.

  1. MozTrap smoketest is created, in-moztrap+ added to the bug in bugzilla
  2. Automate the MozTrap smoketest
  3. Remove the MozTrap smoketest from active testruns, in-qa-automation+ added to the bug in bugzilla

Firefox 13.0.1:

  • [DROPPED] bug 756850 Some combinations of Hebrew vowels and consonants not displayed in certain fonts with harfbuzz
    • Out of scope for Mozmill, will be covered through in-testsuite automation
  • [DROPPED] bug 736731 Hotmail no longer auto-updates
    • Out of scope for Mozmill due to live-site requirements, will be included in manual spotchecks

MozTrap Smoketests

Not Doable

The following tests are not possible to automate due to technical dependencies and scope.

Doable

The following tests are possible to automate and are either assigned or available for anyone to assign to themselves.

Firefox Features

P2 Projects

Project Description Open Bugs
Test Failures Fixing tests which have caused a failure and investigating for possible Firefox bugs mozmill-test-failure
Test Refactoring Updating tests so that they conform to new coding guidelines and modules mozmill-test-refactor
Good First Bug Bugs which have been hand-picked for new contributors good-first-bug
Local Data Writing minimized test cases to be used by the tests (web pages, add-ons, etc) mozmill-test-data
Endurance Tests Writing tests which repeat the same task to stress memory usage mozmill-endurance
Smoketests Writing tests for the most basic functionality mozmill-smoketest
Functional Tests Writing tests for more detailed functionality mozmill-functional
l10n Tests Writing tests to verify compatibility with the numerous languages supported by Firefox mozmill-l10n
Restart Tests Writing tests which verify functionality requiring restart (updates, add-ons, etc) mozmill-restart
Add-ons Tests Writing tests for specific add-ons (Selenium IDE, Google Toolbar, etc) mozmill-addons

Contributing

Before you Begin

Where to get Help

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
Retrieved from "https://wiki.mozilla.org/index.php?title=QA/Desktop_Firefox/Automation&oldid=480971"