canmove, Confirmed users
2,041
edits
B2G/QA/Automation/UI/Strategy: Difference between revisions
B2G/QA/Automation/UI/Strategy (view source)
Revision as of 01:27, 13 February 2015
, 13 February 2015→Challenges
| Line 18: | Line 18: | ||
* Test results have too many spurious failures to sheriff | * Test results have too many spurious failures to sheriff | ||
* Test results only looked at a limited number of times per day | * Test results only looked at a limited number of times per day | ||
* The product is too unstable for acceptance testing during development phases | * The product is too unstable for acceptance testing during development phases | ||
* Acceptance coverage is insufficient to guarantee a quality build | * Acceptance coverage is insufficient to guarantee a quality build | ||
* Community paths are poorly defined and advertised | * Community paths are poorly defined and advertised | ||