B2G/QA/Automation/UI/Strategy: Difference between revisions
< B2G | QA | Automation | UI
Jump to navigation
Jump to search
(→Plan) |
(→Plan) |
||
Line 34: | Line 34: | ||
* [[/Assist with CI tests|Assist the functional teams by increasing coverage]] | * [[/Assist with CI tests|Assist the functional teams by increasing coverage]] | ||
* [[/Port Gaia Integration Python|Move existing | * [[/Port Gaia Integration Python|Move existing Python tests to JS for wider ownership]] | ||
For Community: | For Community: | ||
* [[/Increase Community|Find and implement new approaches to increasing community involvement]] (plan TBD) | * [[/Increase Community|Find and implement new approaches to increasing community involvement]] (plan TBD) |
Revision as of 02:35, 12 February 2015
Team Mandates
- Establish visible subject matter expertise in automation
- Own, expand and maintain QA User Acceptance Test (UAT) automation
- Increase confidence in UAT 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 UAT:
- Streamline current execution for increased responsiveness
- Document how we develop and execute automation
- Develop the Gaia UAT harness, based on Marionette JS
- Increase the coverage using the Gaia UAT harness
For Gaia Integration:
- Assist the functional teams by increasing coverage
- Move existing Python tests to JS for wider ownership
For Community: