B2G/QA/Automation/UI/Strategy/Increase End to end coverage: Difference between revisions

Jump to navigation Jump to search
Line 19: Line 19:
Q2:
Q2:


* Triage of new smoketests for JS UAT backlog [Proposed: Martijn]  
* Triage of new smoketests for Gaia UAT backlog [Proposed: Martijn]  
* Triage of dogfood tests for JS UAT backlog [Proposed: Naoki]
* Triage of dogfood tests for Gaia UAT backlog [Proposed: Naoki]
* Establish JS suites for UATs (depends on passing gate)
* Establish JS suites for Gaia UATs (depends on passing gate)
* Triage of additional areas for JS UAT backlog
* Triage of additional areas for Gaia UAT backlog
* Additions to JS suites for UATs
* Additions to JS suites for Gaia UATs


==Risks==
==Risks==
Line 29: Line 29:
Given the impending move to JS and the need to stabilize the existing tests per the [[../Streamline UAT Execution|Streamlining plan]], it doesn't make sense to continue to expand the Python suite.  
Given the impending move to JS and the need to stabilize the existing tests per the [[../Streamline UAT Execution|Streamlining plan]], it doesn't make sense to continue to expand the Python suite.  


That means we're gated on [[../Develop GaiaTest JS|developing GaiaTest for JS]]. Its risks also apply here.
That means we're gated on [[../Develop Gaia UAT|developing Gaia UAT]]. Its risks also apply here.
canmove, Confirmed users
2,041

edits

Navigation menu