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

Jump to navigation Jump to search
Renaming acceptance to end-to-end
(Renaming acceptance to end-to-end)
 
(9 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=


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


For Acceptance:
For End-to-end:


* [[/Streamline Acceptance Execution|Streamline execution for increased responsiveness with less effort]]
* [[/Streamline End to end Execution|Streamline execution for increased responsiveness with less effort]]
* [[/Document Acceptance 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 Acceptance|Develop Gaia Acceptance, based on Marionette JS]]
* [[/Develop Gaia End to end|Develop Gaia End-to-end, based on Marionette JS]]
* [[/Increase UAT coverage|Increase coverage using Gaia Acceptance]]
* [[/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]] (plan TBD)
* [[/Increase Community|Find and implement new approaches to increasing community involvement]]
Confirmed users
198

edits

Navigation menu