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:28, 11 February 2015
, 11 February 2015no edit summary
(→Risks) |
No edit summary |
||
| Line 1: | Line 1: | ||
=Objective= | |||
Increase the coverage of our UATs so we can more quickly and confidently accept builds and raise errors. | Increase the coverage of our UATs so we can more quickly and confidently accept builds and raise errors. | ||
=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 to the benefit. By implementing more UAT automation, we can increase our impact and free up people for more fruitful exploratory testing. | As QA, we have to do a lot of manual regression testing to know that builds remain acceptable. This takes disproportionate amounts of time to the benefit. By implementing more UAT automation, we can increase our impact and free up people for more fruitful exploratory testing. | ||
=The Solution= | |||
Add all the tests. | |||
=Timeline= | |||
Q2 | Q2 | ||