If you are looking for the Automation Services team, please go to their team page.
- 1 Overview
- 2 The Team
- 3 Weekly Project Status
- 4 How You Can Help
- 5 MozTrap smoketest is created, in-moztrap+ added to the bug in bugzilla
- 6 Automate the MozTrap smoketest
- 7 Remove the MozTrap smoketest from active testruns, in-qa-automation+ added to the bug in bugzilla
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.
You can get in contact with us in a few different ways:
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
Getting Started with Development
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!
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
The following tests are not possible to automate due to technical dependencies and scope.
The following tests are possible to automate and are either assigned or available for anyone to assign to themselves.