B2G/QA/Automation/UI/Strategy: Difference between revisions
< B2G | QA | Automation | UI
Jump to navigation
Jump to search
(Renaming acceptance to end-to-end) |
|||
(4 intermediate revisions by one other user not shown) | |||
Line 2: | Line 2: | ||
* Establish visible subject matter expertise and impact in test and automation | * Establish visible subject matter expertise and impact in test and automation | ||
* Own, expand and maintain QA | * Own, expand and maintain QA End-to-end automation | ||
* Increase confidence in | * Increase confidence in End-to-end 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 | ||
Line 18: | Line 18: | ||
* Test results have too many spurious failures to sheriff | * Test results have too many spurious failures to sheriff | ||
* Test results only looked at a limited number of times per day | * Test results only looked at a limited number of times per day | ||
* The product is too unstable for end-to-end testing during development phases | |||
* End-to-end coverage is insufficient to guarantee a quality build | |||
* Community paths are poorly defined and advertised | * Community paths are poorly defined and advertised | ||
=Plan= | =Plan= | ||
* [[/Integration vs | * [[/Integration vs End to end|Separate automation concerns for Integration and End-to-end tests]] | ||
For | For End-to-end: | ||
* [[/Streamline | * [[/Streamline End to end Execution|Streamline execution for increased responsiveness with less effort]] | ||
* [[/Document | * [[/Document End to end Automation|Document how we develop and execute End-to-end automation]] | ||
* [[/Develop Gaia | * [[/Develop Gaia End to end|Develop Gaia End-to-end, based on Marionette JS]] | ||
* [[/Increase | * [[/Increase End to end coverage|Increase coverage using Gaia End-to-end]] | ||
For Integration: | For Integration: | ||
Line 38: | Line 40: | ||
For Community: | For Community: | ||
* [[/Increase Community|Find and implement new approaches to increasing community involvement]] | * [[/Increase Community|Find and implement new approaches to increasing community involvement]] |
Latest revision as of 17:52, 17 November 2015
Team Mandates
- Establish visible subject matter expertise and impact in test and automation
- Own, expand and maintain QA End-to-end automation
- Increase confidence in End-to-end 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
- The product is too unstable for end-to-end testing during development phases
- End-to-end coverage is insufficient to guarantee a quality build
- Community paths are poorly defined and advertised
Plan
For End-to-end:
- Streamline execution for increased responsiveness with less effort
- Document how we develop and execute End-to-end automation
- Develop Gaia End-to-end, based on Marionette JS
- Increase coverage using Gaia End-to-end
For Integration:
- Assist the functional teams by increasing Gaia Integration coverage
- Port Gaia Integration Python tests to JavaScript for wider ownership
For Community: