canmove, Confirmed users
2,041
edits
B2G/QA/Automation/UI/Best Practices: Difference between revisions
Jump to navigation
Jump to search
B2G/QA/Automation/UI/Best Practices (view source)
Revision as of 17:10, 23 March 2015
, 23 March 2015→Tests that check UI mechanics
| Line 28: | Line 28: | ||
* 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. | ||
* Should still abstract selectors as these change frequently and aren't directly important to the test. | * Should still abstract selectors as these change frequently and aren't directly important to the test. | ||
* Will not generally correspond with a traditionally-scripted QA test. They'll be much shorter. | * Will not generally correspond with a traditionally-scripted QA test. They'll be much shorter and simpler, more like a single test step. | ||
* Should have almost no logic whatsoever. | * Should have almost no logic whatsoever. | ||