canmove, Confirmed users
2,041
edits
B2G/QA/Automation/UI/Strategy/Increase End to end coverage: Difference between revisions
B2G/QA/Automation/UI/Strategy/Increase End to end coverage (view source)
Revision as of 04:27, 11 February 2015
, 11 February 2015→Risks
(Created page with "=Strategy: Increase UAT Coverage= ==Objective== Increase the coverage of our UATs so we can more quickly and confidently accept builds and raise errors. ==The Problem== As...") |
(→Risks) |
||
| Line 25: | Line 25: | ||
==Risks== | ==Risks== | ||
Given the impending move to JS and the need to stabilize the | Given the impending move to JS and the need to stabilize the existing tests per the [[../Streamlining 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 GaiaTest JS|developing GaiaTest for JS]]. Its risks also apply here. | ||