B2G/QA/Automation/UI/Strategy/Increase End to end coverage: Difference between revisions
| Line 19: | Line 19: | ||
Q2: | Q2: | ||
* Triage of new smoketests for | * Triage of new smoketests for Gaia UAT backlog [Proposed: Martijn] | ||
* Triage of dogfood tests for | * 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 | * 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 | That means we're gated on [[../Develop Gaia UAT|developing Gaia UAT]]. Its risks also apply here. | ||
Revision as of 02:34, 12 February 2015
Objective
Increase the coverage of our UATs so we can more quickly and confidently accept builds and raise errors.
Challenges Addressed
- Development and QA have different approaches and needs from UI testing
The Problem
As QA, we have to do a lot of manual regression testing to know that builds remain acceptable. This takes disproportionate amounts of time compared to the benefit of verifying the absence of bugs. By implementing more UAT automation, we can increase our impact and free up people for more fruitful exploratory testing.
The Solution
Add any tests that we plan to accept builds on. Don't consider appropriateness for CI.
Timeline
Q2:
- Triage of new smoketests for Gaia UAT backlog [Proposed: Martijn]
- Triage of dogfood tests for Gaia UAT backlog [Proposed: Naoki]
- Establish JS suites for Gaia UATs (depends on passing gate)
- Triage of additional areas for Gaia UAT backlog
- Additions to JS suites for Gaia UATs
Risks
Given the impending move to JS and the need to stabilize the existing tests per the Streamlining plan, it doesn't make sense to continue to expand the Python suite.
That means we're gated on developing Gaia UAT. Its risks also apply here.