Confirmed users
3,816
edits
Auto-tools/Goals/2011Q4: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
= Official Q4 Goals = | |||
* {{ok|Achieve and maintain a 5% or less intermittent orange rate for Android automation (talos and tests) to achieve parity with desktop intermittent orange rates.}} | * {{ok|Achieve and maintain a 5% or less intermittent orange rate for Android automation (talos and tests) to achieve parity with desktop intermittent orange rates.}} | ||
** {{ok|Land modifications to make it easier for developers to run Android talos (to make it easier to debug failures)}} | ** {{ok|Land modifications to make it easier for developers to run Android talos (to make it easier to debug failures)}} | ||
| Line 13: | Line 14: | ||
** {{ok|Deploy Regression User Responsiveness (peptest) on desktop production automation}} | ** {{ok|Deploy Regression User Responsiveness (peptest) on desktop production automation}} | ||
== | == Crucial Projects == | ||
These projects must be completed to achieve the above goals. | These projects must be completed to achieve the above goals. | ||
| Line 72: | Line 73: | ||
=== '''GOAL:''' User Responsiveness Automation === | === '''GOAL:''' User Responsiveness Automation === | ||
==== Talos User Responsiveness ==== | |||
* '''Q4 Outcomes''' | |||
** {{ok|Deploy into production for desktop and android}} | |||
** {{ok|Finalize equation for responsiveness metric}} | |||
** {{ok|Determine if test can be deployed as addition to Tp5}} | |||
** {{ok|Work with developers and Releng for deployment}} | |||
* '''Community Involvement''' | |||
** Ensure blogs, newsgroups updated with changes and notices surrounding this system | |||
* '''Depends on''' | |||
** Developers creating the metric | |||
** Release Engineering for deployment | |||
** Stable android automation | |||
==== Peptest User Responsiveness ==== | |||
* '''Q4 Outcomes''' | |||
** {{ok|Land test harness in m-c with full integration (make targets etc)}} | |||
** {{ok|Deploy into production for desktop automation}} | |||
** {{ok|Provide simple API for driving UI (post-landing, stretch)}} | |||
* '''Community Involvement''' | |||
** Ensure community is up to date on the new harness and expectations surrounding it. | |||
** Ensure log parsers ready to accept the log format and developers educated on how to run it and parse the data from it | |||
* '''Depends on''' | |||
** Mozbase/mozharness | |||
** Release Engineering for deployment | |||
** Developers creating the metric for Talos User Responsiveness | |||
** Mozmill E10s (for driving API) | |||
== Supporting Projects == | == Supporting Projects == | ||
Many of our projects are inter-related, and there are many supporting projects that we want to call out as they are important and cannot be entirely neglected in favor of these goals. This section calls these out. | Many of our projects are inter-related, and there are many supporting projects that we want to call out as they are important and cannot be entirely neglected in favor of these goals. This section calls these out. | ||
| Line 147: | Line 179: | ||
* '''Interconnections''' | * '''Interconnections''' | ||
** REST API and Pulse integration directly improve Orange Factor, which aids us in making our test and performance automation more stable. | ** REST API and Pulse integration directly improve Orange Factor, which aids us in making our test and performance automation more stable. | ||
== Back Burner == | |||
These projects are on the back burner for the quarter. We'll aid with support and maintenance as needed, but they will not be our primary focus | |||
* Autolog | |||
* War on Orange | |||
* Speed Tests | |||
* DXR automation | |||
* TPS (crossweave) | |||