B2G/QA/Automation/UI/Strategy: Difference between revisions
< B2G | QA | Automation | UI
Jump to navigation
Jump to search
No edit summary |
|||
| Line 2: | Line 2: | ||
* Establish visible subject matter expertise in automation | * Establish visible subject matter expertise in automation | ||
* Own, expand and maintain QA | * Own, expand and maintain QA acceptance test automation | ||
* Increase confidence in | * Increase confidence in acceptance test automation | ||
* Provide expert assistance to improve all phases of UI test coverage | * Provide expert assistance to improve all phases of UI test coverage | ||
* Catch problems quickly and effectively | * Catch problems quickly and effectively | ||
Revision as of 23:48, 12 February 2015
Team Mandates
- Establish visible subject matter expertise in automation
- Own, expand and maintain QA acceptance test automation
- Increase confidence in acceptance test automation
- Provide expert assistance to improve all phases of UI test coverage
- Catch problems quickly and effectively
- Increase community support for FxOS QA
- Increase quality of and confidence in the product
Challenges
- Automation systems and concerns are poorly documented
- Development and QA have different approaches and needs from UI testing
- UI tests have had no developer support, largely because of Python implementation
- Team has been blocked too much by cross-team dependencies
- Test results are hidden in Jenkins
- Test results have too many spurious failures to sheriff
- Test results only looked at a limited number of times per day
- Community paths poorly defined and advertised
Plan
For Gaia UATs:
- Streamline current execution for increased responsiveness
- Document how we develop and execute Acceptance automation
- Develop the Gaia Acceptance harness, based on Marionette JS
- Increase the coverage using the Gaia Acceptance harness
For Gaia Integration:
- Assist the functional teams by increasing coverage
- Move existing Python tests to JS for wider ownership
For Community: