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:50, 23 March 2015
, 23 March 2015→Explicitness
| Line 60: | Line 60: | ||
* Tests are frequently the only documentation of application behavior | * Tests are frequently the only documentation of application behavior | ||
* Any extraneous detail in the test interferes with clarity and ability to review for correctness. | |||
* Test code should be absolutely explicit about behavior at their functional level of [[#Abstraction|abstraction]]. | * Test code should be absolutely explicit about behavior at their functional level of [[#Abstraction|abstraction]]. | ||
* Test code should be | * Test code should be implicit about behavior below their functional level of [[#Abstraction|abstraction]]. | ||
* Reading a test should tell you as closely as possible what the test ''means'' to do, no more and no less. | * Reading a test should tell you as closely as possible what the test ''means'' to do, no more and no less. | ||