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 12: | Line 12: | ||
** {{ok|Deploy Talos User Responsiveness test on desktop and android automation}} | ** {{ok|Deploy Talos User Responsiveness test on desktop and android automation}} | ||
** {{ok|Deploy Regression User Responsiveness (peptest) on desktop production automation}} | ** {{ok|Deploy Regression User Responsiveness (peptest) on desktop production automation}} | ||
== Actions on Goals == | |||
== Supporting Projects == | == Supporting Projects == | ||
| Line 43: | Line 45: | ||
=== Mozbase === | === Mozbase === | ||
* '''Q4 Outcomes''' | * '''Q4 Outcomes''' | ||
** | ** {{ok|Work with Release Engineering MozHarness to deploy a MozHarness/MozBase Talos system}} | ||
** {{ok|Ensure mozbase utilities are robust enough underpinnings for Peptest}} | |||
** {{ok|Have our own automated tests running for Mozbase utilities to ensure their robustness (reporting to autolog)}} | |||
* '''Community Involvement''' | |||
** Use github to pull in new contributors toward our work | |||
** Publicize what benefits these changes will bring | |||
* '''Interconnections''' | |||
** Aids with the "make talos easier for developers to run" sub goal in "Make android automation more reliable" | |||
** Crucial support for PepTest in user responsiveness goal. | |||
=== W3C Browser Test Protocol Effort === | |||
* '''Q4 Outcomes''' | |||
** Attend meeting, ensure actions created from it are helpful to our efforts | |||
** Situate ourselves for greater involvement in Q1. | |||
* '''Community Involvement''' | |||
** This is a community involvement goal | |||
* '''Interconnections''' | |||
** The JSON protocol that marionette is using will be based upon the protocol developed by this group. | |||
=== Mozmill E10S === | |||
* '''Q4 Outcomes''' | |||
** Adapt the harness to run in E10S firefox and fennec | |||
** All Mutt tests should pass in E10S mode | |||
* '''Community Involvement''' | |||
** Publicize the "lessons learned" for other addon developers to use | |||
* '''Interconnections''' | |||
** The later phases of Peptest will re-use some of the mozmill UI driver code to provide a simple API for driving the browser to perform user actions. | |||
=== Bugzilla === | |||
* '''Q4 Outcomes''' | |||
** Complete Bugzilla REST API to be native to bugzilla with all parameters of the existing REST API | |||
** Drive creation of plan for Pulse integration with bugzilla (involves IT coordination, experimentation) | |||
** Deploy 4.2 (provided upstream is completed). | |||
* '''Community Involvement''' | |||
** Be more public about what these changes (REST, pulse, 4.2 etc) bring to the wider mozilla community. | |||
* '''Interconnections''' | |||
** REST API and Pulse integration directly improve Orange Factor, which aids us in making our test and performance automation more stable. | |||