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:09, 23 March 2015
, 23 March 2015→Tests that check UI mechanics
| Line 26: | Line 26: | ||
* Should not delegate strings of UI calls used in a test to functional-style Page Objects or similar high level abstraction mechanisms. They own that sequence. | * Should not delegate strings of UI calls used in a test to functional-style Page Objects or similar high level abstraction mechanisms. They own that sequence. | ||
* Should, however, abstract selectors as these change frequently. | * Should, however, abstract selectors as these change frequently. | ||
* Will be very fragile, as any change in UI assumption will | * Will be very fragile, as any change in UI assumption will require changes to 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. | * Will not generally correspond with a traditionally-scripted QA test. They'll be much shorter. | ||