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 functional behavior
| Line 54: | Line 54: | ||
* Will consist of a string of functions at high-level, such as calendar.createEntry(...) and calendar.getEntry() == defaultEntry. | * Will consist of a string of functions at high-level, such as calendar.createEntry(...) and calendar.getEntry() == defaultEntry. | ||
* Will be longer and more complex, so need to be at a higher level of abstraction to promote reuse and keep clarity. | * Will be longer and more complex, so need to be at a higher level of abstraction to promote reuse and keep clarity. | ||
* Will more closely correspond to a full QA-scripted test. | |||
* Can have basic logic to the extent a user would also perform that logic as part of a scenario. They should still optimize for straightforward scenarios. | * Can have basic logic to the extent a user would also perform that logic as part of a scenario. They should still optimize for straightforward scenarios. | ||