Confirmed users
3,816
edits
Auto-tools/Goals/2011Q4: Difference between revisions
Jump to navigation
Jump to search
no edit summary
(port items from http://etherpad.mozilla.com:9000/WlDbiUz0Zt) |
No edit summary |
||
| Line 5: | Line 5: | ||
* {{ok|Expand and enhance our test and performance automation to anticipate and address needs for Fennec and B2G.}} | * {{ok|Expand and enhance our test and performance automation to anticipate and address needs for Fennec and B2G.}} | ||
** {{ok|Deliver video capture data from an alive test (Ts/Tp) an a "driver" test (Tuser) from eideticker to developers for analysis. Stretch: have system ready for duplication by end of Quarter}} | ** {{ok|Deliver video capture data from an alive test (Ts/Tp) an a "driver" test (Tuser) from eideticker to developers for analysis. Stretch: have system ready for duplication by end of Quarter}} | ||
** {{ok|Deploy Talos RSS metrics in Android production}} | ** {{ok|Deploy Talos RSS metrics in Android production}} | ||
** {{ok|Land marionette with ability to "runscript" in B2G context and enough action support to run Tuser eideticker test.}} | ** {{ok|Land marionette with ability to "runscript" in B2G context and enough action support to run Tuser eideticker test.}} | ||
** {{ok|Land enhancements to special powers to entirely remove enablePrivilege from all testing frameworks}} | |||
* {{ok|Deploy user responsiveness automation into production}} | * {{ok|Deploy user responsiveness automation into production}} | ||
| Line 13: | Line 13: | ||
** {{ok|Deploy Regression User Responsiveness (peptest) on desktop production automation}} | ** {{ok|Deploy Regression User Responsiveness (peptest) on desktop production automation}} | ||
== | == 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. | |||
=== Bughunter === | |||
* '''Q4 Outcomes''' | |||
** {{ok|UI Deployed, UI taken through find/fix cycle}} | |||
** {{ok|Conduct demo/training for QA, Dev, and Product Mgmt on tool}} | |||
** {{ok|Create plan for soccoro integration}} | |||
*'''Community Involvement''' | |||
** Targeted involvement with other areas of Mozilla (see training outcome) | |||
* '''Interconnections''' | |||
** Increasing quality and security for the gecko platform by providing good data on crashes. | |||
** Visualization technologies will be repurposed | |||
** Future: Android integration, re-using technology for "classify the web" effort | |||
=== Pandaboards === | |||
* '''Q4 Outcomes''' | |||
** {{ok|Create repeatable, deployable build/flash system to get a functioning board running}} | |||
** {{ok|Analyze results from unit and performance tests on board, but not in production this quarter}} | |||
* '''Community Involvement''' | |||
** Working with linaro, having presence in pandaboard community, publicizing the created scripts | |||
* '''Interconnections''' | |||
** Aids with the "expand mobile test and performance automation" Q4 goal. | |||
=== Mozbase === | |||
* '''Q4 Outcomes''' | |||
** | |||