canmove, Confirmed users
2,041
edits
B2G/QA/Automation/UI/Best Practices: Difference between revisions
B2G/QA/Automation/UI/Best Practices (view source)
Revision as of 16:49, 23 March 2015
, 23 March 2015→Tests that check UI mechanics
| Line 28: | Line 28: | ||
* Will be very fragile, as any change in UI assumption will break all tests making that assumption. | * Will be very fragile, as any change in UI assumption will break all tests making that assumption. | ||
* Should therefore be kept very short and isolated, with no extended sequences. Ideally, one changed assumption = one broken test. | * Should therefore be kept very short and isolated, with no extended sequences. Ideally, one changed assumption = one broken test. | ||
* Will not generally correspond with a traditionally-scripted QA test. They'll be much shorter. | |||
* Should have almost no logic whatsoever. | * Should have almost no logic whatsoever. | ||