canmove, Confirmed users
2,041
edits
B2G/QA/Automation/UI/Strategy/Integration vs End to end: Difference between revisions
Jump to navigation
Jump to search
B2G/QA/Automation/UI/Strategy/Integration vs End to end (view source)
Revision as of 18:13, 11 February 2015
, 11 February 2015→Different Contexts
| Line 58: | Line 58: | ||
* CI tests can never fail unless there's a defective code change. They must be unambiguous. | * CI tests can never fail unless there's a defective code change. They must be unambiguous. | ||
* UATs can still fail non-deterministically if | * UATs can still fail non-deterministically if they are reliable enough to be a net gain. | ||
* CI tests are maintained by development to give themselves confidence in code changes | * CI tests are maintained by development to give themselves confidence in code changes | ||