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

From MozillaWiki
< B2G‎ | QA‎ | Automation‎ | UI
Jump to navigation Jump to search
Line 28: Line 28:
* [[/Streamline UAT Execution|Streamline current execution for increased responsiveness]]
* [[/Streamline UAT Execution|Streamline current execution for increased responsiveness]]
* [[/Document FxOS UI QA Automation|Document how we develop and execute automation]]
* [[/Document FxOS UI QA Automation|Document how we develop and execute automation]]
* [[/Develop GaiaTest JS|Develop the Gaia UAT harness, based on Marionette JS]]
* [[/Develop Gaia UAT|Develop the Gaia UAT harness, based on Marionette JS]]
* [[/Increase UAT coverage|Increase the coverage using the Gaia UAT harness]]
* [[/Increase UAT coverage|Increase the coverage using the Gaia UAT harness]]



Revision as of 02:32, 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:

For Gaia Integration:

For Community: