canmove, Confirmed users
2,041
edits
B2G/QA/Automation/UI/Strategy/Integration vs End to end: Difference between revisions
B2G/QA/Automation/UI/Strategy/Integration vs End to end (view source)
Revision as of 00:58, 13 February 2015
, 13 February 2015→Two different suites of UI automation
| Line 35: | Line 35: | ||
** Coverage is restricted because of these rules | ** Coverage is restricted because of these rules | ||
** Will be run prior to each commit and can prevent a bad code change from landing | ** Will be run prior to each commit and can prevent a bad code change from landing | ||
** Scope, | ** Scope, depth, and maintenance is owned by functional teams as part of their code | ||
** Small isolated tests can be checked in with code changes immediately | ** Small isolated tests can be checked in with code changes immediately | ||
** Is sheriffed reliably and quickly through long-standing and established process | ** Is sheriffed reliably and quickly through long-standing and established process | ||
| Line 45: | Line 45: | ||
** Has much less restriction than Integration, so long as time spent triaging failures isn't extreme | ** Has much less restriction than Integration, so long as time spent triaging failures isn't extreme | ||
** Runs after each Tinderbox or candidate build to quickly find full-stack bugs | ** Runs after each Tinderbox or candidate build to quickly find full-stack bugs | ||
** Scope, | ** Scope, depth, and maintenance is owned by QA | ||
** Tests can be created after area is delivered and UI is stable enough to make cost acceptable | ** Tests can be created after area is delivered and UI is stable enough to make cost acceptable | ||
** Must be sheriffed by QA, via a combination of alerts and result reviews | ** Must be sheriffed by QA, via a combination of alerts and result reviews | ||