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

Jump to navigation Jump to search
Line 22: Line 22:
* Triage of new smoketests for Gaia Acceptance backlog
* Triage of new smoketests for Gaia Acceptance backlog
* Triage of dogfood tests for Gaia Acceptance backlog
* Triage of dogfood tests for Gaia Acceptance backlog
* Establish JS suites for Gaia Acceptance (depends on passing gate)
* Establish JS suites for Gaia Acceptance
* Triage of additional areas for Gaia Acceptance backlog
* Triage of additional areas for Gaia Acceptance backlog
* Additions to JS suites for Gaia Acceptance tests
* Additions to JS suites for Gaia Acceptance tests
Line 28: Line 28:
==Risks==
==Risks==


Given the impending move to JS and the need to stabilize the existing tests per the [[../Streamline Acceptance 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 Acceptance Execution|Streamlining plan]], it doesn't make sense to continue to expand the Python suite.


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

edits

Navigation menu