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

From MozillaWiki
< B2G‎ | QA‎ | Automation‎ | UI
Jump to navigation Jump to search
Line 29: Line 29:
* [[/Document Acceptance Automation|Document how we develop and execute Acceptance automation]]
* [[/Document Acceptance Automation|Document how we develop and execute Acceptance automation]]
* [[/Develop Gaia Acceptance|Develop Gaia Acceptance, based on Marionette JS]]
* [[/Develop Gaia Acceptance|Develop Gaia Acceptance, based on Marionette JS]]
* [[/Increase UAT coverage|Increase the coverage using Gaia Acceptance]]
* [[/Increase UAT coverage|Increase coverage using Gaia Acceptance]]


For Gaia Integration:
For Gaia Integration:

Revision as of 00:30, 13 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 Acceptance:

For Gaia Integration:

For Community: