B2G/QA/Automation/UI/Strategy: Difference between revisions

From MozillaWiki
< B2G‎ | QA‎ | Automation‎ | UI
Jump to navigation Jump to search
(Renaming acceptance to end-to-end)
 
(18 intermediate revisions by one other user not shown)
Line 1: Line 1:
=Team Mandates=
=Team Mandates=


* Establish visible subject matter expertise in automation
* Establish visible subject matter expertise and impact in test and automation
* Own, expand and maintain QA acceptance test automation
* Own, expand and maintain QA End-to-end automation
* Increase confidence in acceptance test automation
* 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
* Community paths poorly defined and advertised
* 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=
=Plan=


* [[/Gaia Integration vs Gaia UAT|Separate automation concerns for Integration and Acceptance tests]]
* [[/Integration vs End to end|Separate automation concerns for Integration and End-to-end tests]]


For Gaia Acceptance:
For End-to-end:


* [[/Streamline UAT Execution|Streamline execution for increased responsiveness with less effort]]
* [[/Streamline End to end Execution|Streamline execution for increased responsiveness with less effort]]
* [[/Document FxOS UI QA Automation|Document how we develop and execute Acceptance automation]]
* [[/Document End to end Automation|Document how we develop and execute End-to-end automation]]
* [[/Develop Gaia UAT|Develop the Gaia Acceptance harness, based on Marionette JS]]
* [[/Develop Gaia End to end|Develop Gaia End-to-end, based on Marionette JS]]
* [[/Increase UAT coverage|Increase the coverage using the Gaia Acceptance harness]]
* [[/Increase End to end coverage|Increase coverage using Gaia End-to-end]]


For Gaia Integration:
For Integration:


* [[/Assist with CI tests|Assist the functional teams by increasing coverage]]
* [[/Assist with CI tests|Assist the functional teams by increasing Gaia Integration coverage]]
* [[/Port Gaia Integration Python|Move existing Python tests to JS for wider ownership]]
* [[/Port Gaia Integration Python|Port Gaia Integration Python tests to JavaScript 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]]

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:

For Integration:

For Community: