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...")
 
Line 4: Line 4:


== Q1 2014 ==
== Q1 2014 ==
* Get the MetroFirefox tests running reliably (with a max 5% failure rate) in CI production at latest at Feb 12th
* {{new|}} Get the MetroFirefox tests running reliably (with a max 5% failure rate) in CI production at latest at Feb 12th
* Setup testing environment for Firefox accounts before it gets shipped on March 17th and work with the A-Team if further help is necessary
* {{new|}} Setup testing environment for Firefox accounts before it gets shipped on March 17th and work with the A-Team if further help is necessary
* 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
* {{new|}} 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
* {{new|}} 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 ===
=== Stretched Goals ===
* Getting PuppetAgain support for Ubuntu started so we can lower the amount of manual maintenance of the CI cluster in the future
* {{new|}} Getting PuppetAgain support for Ubuntu started so we can lower the amount of manual maintenance of the CI cluster in the future
* Increase the number of Firefox locales to test by letting each locale run at least once a week
* {{new|}} Increase the number of Firefox locales to test by letting each locale run at least once a week

Revision as of 22:15, 29 January 2014

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 around 10 community members working on a weekly basis
  • 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

Q1 2014

  • [NEW] Get the MetroFirefox tests running reliably (with a max 5% failure rate) in CI production at latest at Feb 12th
  • [NEW] Setup testing environment for Firefox accounts before it gets shipped on March 17th and work with the A-Team if further help is necessary
  • [NEW] Organize 2 Automation training testdays for contributors to get them started and guided through the lifecycle of the test creation process. Revamp the Crowd extension for a better start
  • [NEW] 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

  • [NEW] Getting PuppetAgain support for Ubuntu started so we can lower the amount of manual maintenance of the CI cluster in the future
  • [NEW] Increase the number of Firefox locales to test by letting each locale run at least once a week