canmove, Confirmed users, Bureaucrats and Sysops emeriti
4,714
edits
QA/Test Automation/2011-01-12: Difference between revisions
Jump to navigation
Jump to search
→Goals Overview
| Line 17: | Line 17: | ||
* [https://intranet.mozilla.org/QA/Q12011_QAgoals#Automation_QA_Goals Q1 goals] planning | * [https://intranet.mozilla.org/QA/Q12011_QAgoals#Automation_QA_Goals Q1 goals] planning | ||
* Proposals | |||
** Triggered Update Tests | |||
*** Integrate triggered Mozmill update tests into nightly automation process | |||
*** what about release candidate builds? For Q2? | |||
** Endurance Tests | |||
*** Create suite of Mozmill tests to stress-test Firefox in different areas | |||
*** Performance tests | |||
** Module Refactoring | |||
*** Finalize the project by updating modules and tests | |||
**** Only for mostly used modules and tests for the beginning (focus areas) | |||
**** Updates per component | |||
** Collaborate with development teams to get XXX BFT tests automated | |||
*** We never found a good way to specify a realistic goal, whether via number of tests nor per component. Do we have other options? | |||
*** Given the Firefox 4 priority and other goals, how much time we would have this quarter? | |||
*** Should we better move our efforts to keep the testsuite green? | |||
** Testing Server | |||
*** Setting up a testing server which allows kill our dependencies on external websites. | |||
= Risky Goals = | = Risky Goals = | ||