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 13: | Line 13: | ||
** {{ok|Deploy Regression User Responsiveness (peptest) on desktop production automation}} | ** {{ok|Deploy Regression User Responsiveness (peptest) on desktop production automation}} | ||
== | == Goal Projects == | ||
These projects must be completed to achieve the above goals. | |||
=== '''GOAL:''' Improve Android Stability === | |||
* '''Q4 Outcomes''' | |||
** {{ok|Reproduce and fix intermittent android issues}} | |||
** {{done|Add Android Talos to Orange Factor to aid in tracking}} | |||
** {{ok|"Make Android Remote Talos" must be landed}} | |||
** {{ok|Create specialpowers core to use in other tests, may not prove necessary}} | |||
* '''Community Involvement''' | |||
** All these changes directly impact developers, ensure good publicizing (blog, newsgoup etc) done around these changes | |||
* '''Depends On''' | |||
** Orange Factor | |||
** Mozbase/Mozharness | |||
** SpecialPowers API work | |||
=== '''GOAL:''' Expand Android Performance and Unit Tests === | |||
==== Eideticker ==== | |||
* '''Q4 Outcomes''' | |||
** {{ok|Deliver video capture data from an alive test (Ts/Tp) an a "driver" test (Tuser) from eideticker to developers for analysis.}} | |||
** {{ok|Have system stable enough to be ready for duplication in MV by end of quarter (stretch)}} | |||
** {{ok|Define two tests for completion at end of Quarter}} | |||
** {{ok|Integrate with marionette JSON protocol to drive device under test}} | |||
** {{ok|Potentially use JSON protocol and shim (supplied by selenium project) to drive non-gecko browsers on device (stretch/Q1)}} | |||
* '''Community Involvement''' | |||
** Cross-team project, ensure and maintain feedback loops with teams Eideticker is being developed for - close customer integration | |||
* '''Depends on''' | |||
** Marionette | |||
** Mozbase/Talos | |||
==== Marionette ==== | |||
* '''Q4 Outcomes''' | |||
** {{ok|Create receiver for JSON protocol}} | |||
** {{ok|Implement enough action to support the Eideticker tests}} | |||
** {{ok|Land in m-c by end of quarter}} | |||
* '''Community Involvement''' | |||
** Cross-team project, ensure and maintain feedback loops with teams Eideticker is being developed for - close customer integration. | |||
* '''Depends on''' | |||
** Developer Tools Remote Debugging Code | |||
** A11y interfaces | |||
** W3C Browser Test Protocol definition (soft dependency) | |||
==== SpecialPowers API ==== | |||
* '''Q4 Outcomes''' | |||
** {{ok|Remove all enablePrivilege calls in all test frameworks and land patches in m-c}} | |||
* '''Community Involvement''' | |||
** Be public and visible, try to recruit JS hackers to aid with project, engage developers to help expand APIs as needed | |||
* '''Depends on''' | |||
** Developer aid (original test writers usually) when issues arise | |||
=== '''GOAL:''' User Responsiveness Automation === | |||
== 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. | ||