QA/Automation/Goals: Difference between revisions

From MozillaWiki
< QA‎ | Automation
Jump to navigation Jump to search
(Created page with "== Yearly Goals for 2014 == * Extend the work with the community and get them more integrated into our existing projects. As a result we want to have an average number of arou...")
 
(Q3 2015 goals)
 
(23 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Yearly Goals for 2014 ==
== Q3 2015 ==
* Extend the work with the community and get them more integrated into our existing projects. As a result we want to have an average number of around 10 community members working on a weekly basis
* '''Replace custom test runner script for firefox-ui-tests with mozharness when executing tests via Jenkins''' ([https://bugzilla.mozilla.org/show_bug.cgi?id=1192369|Bug 1192369])
* Assist the QA team and each interested community member in every of our top-level projects, and help them pro-actively in improving their skills for defining and implementing automated tests and extending or fixing test framework features
** Improve overall stability and result reporting to treeherder
** Standardized execution of tests for an easy change of the execution platform (e.g. taskcluster)
* '''Investigate requirements for running firefox-ui-tests via taskcluster instead of Jenkins''' ([https://bugzilla.mozilla.org/show_bug.cgi?id=1192371|Bug 1192371])
** Joined work with taskcluster team to define requirements
** Create roadmap for taskcluster integration


== Q1 2014 ==
=== Stretched Goals ===
* Get the MetroFirefox tests running reliably (with a max 5% failure rate) in CI production at latest at Feb 12th
* mozdownload has to download builds from AWS via taskcluster ([https://github.com/mozilla/mozdownload/issues/278|issue 278])
* Setup testing environment for Firefox accounts before it gets shipped on March 17th and work with the A-Team if further help is necessary
* Developer documentation for Firefox UI Tests
* Organize 2 Automation training testdays for contributors to get them started and guided through the lifecycle of the test creation process. Revamp the [https://addons.mozilla.org/en-US/firefox/addon/mozmill-crowd/|Mozmill Crowd extension] for a better start
* Rework the software update tests to be based on a state machine, so that they are able to run multiple updates in a row


=== Stretched Goals ===
== Goals Proposals ==
* Getting PuppetAgain support for Ubuntu started so we can lower the amount of manual maintenance of the CI cluster in the future
If you have ideas and want to propose those as a goal for our team for the next quarters, please go to our [https://etherpad.mozilla.org/firefox-automation-goals goals collection etherpad] and enter them all together with your name.
* Increase the number of Firefox locales to test by letting each locale run at least once a week

Latest revision as of 13:19, 8 August 2015

Q3 2015

  • Replace custom test runner script for firefox-ui-tests with mozharness when executing tests via Jenkins (1192369)
    • Improve overall stability and result reporting to treeherder
    • Standardized execution of tests for an easy change of the execution platform (e.g. taskcluster)
  • Investigate requirements for running firefox-ui-tests via taskcluster instead of Jenkins (1192371)
    • Joined work with taskcluster team to define requirements
    • Create roadmap for taskcluster integration

Stretched Goals

  • mozdownload has to download builds from AWS via taskcluster (278)
  • Developer documentation for Firefox UI Tests

Goals Proposals

If you have ideas and want to propose those as a goal for our team for the next quarters, please go to our goals collection etherpad and enter them all together with your name.

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