B2G/QA/Automation/UI/Strategy/Increase End to end coverage: Difference between revisions
No edit summary |
|||
| Line 1: | Line 1: | ||
=Objective= | =Objective= | ||
Increase the coverage of our | Increase the coverage of our Acceptance tests so we can more quickly and confidently accept builds and raise errors. | ||
=Challenges Addressed= | =Challenges Addressed= | ||
| Line 9: | Line 9: | ||
=The Problem= | =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 | 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 Acceptance automation, we can increase our impact and free up people for more fruitful exploratory testing. | ||
=The Solution= | =The Solution= | ||
Add any tests that we plan to accept builds on. Don't consider appropriateness for | Add any tests that we plan to accept builds on. Don't consider appropriateness for Gaia Integration. | ||
=Timeline= | =Timeline= | ||
| Line 19: | Line 19: | ||
Q2: | Q2: | ||
* Triage of new smoketests for Gaia | * Triage of new smoketests for Gaia Acceptance backlog [Proposed: Martijn] | ||
* Triage of dogfood tests for Gaia | * Triage of dogfood tests for Gaia Acceptance backlog [Proposed: Naoki] | ||
* Establish JS suites for Gaia UATs (depends on passing gate) | * Establish JS suites for Gaia UATs (depends on passing gate) | ||
* Triage of additional areas for Gaia | * Triage of additional areas for Gaia Acceptance backlog | ||
* Additions to JS suites for Gaia | * Additions to JS suites for Gaia Acceptance tests | ||
==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 Gaia UAT|developing Gaia | That means we're gated on [[../Develop Gaia UAT|developing Gaia Acceptance]]. Its risks also apply here. | ||
Revision as of 00:08, 13 February 2015
Objective
Increase the coverage of our Acceptance tests 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 Acceptance 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 Gaia Integration.
Timeline
Q2:
- Triage of new smoketests for Gaia Acceptance backlog [Proposed: Martijn]
- Triage of dogfood tests for Gaia Acceptance backlog [Proposed: Naoki]
- Establish JS suites for Gaia UATs (depends on passing gate)
- Triage of additional areas for Gaia Acceptance backlog
- Additions to JS suites for Gaia Acceptance tests
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 Acceptance. Its risks also apply here.