Confirmed users
9,511
edits
QA/Execution/Web Testing/Selenium Guidelines: Difference between revisions
Jump to navigation
Jump to search
QA/Execution/Web Testing/Selenium Guidelines (view source)
Revision as of 18:09, 14 January 2010
, 14 January 2010→Some good practices
No edit summary |
|||
| Line 3: | Line 3: | ||
= Some good practices = | = Some good practices = | ||
*Give meaningful names to test cases. Example:"Advanced search test case" is a very vague name which does not specify what exactly you intend to verify. "Verify platform specific search for firefox addons" is more specific. | *Give meaningful names to test cases. Example: "Advanced search test case" is a very vague name which does not specify what exactly you intend to verify. "Verify platform specific search for firefox addons" is more specific. | ||
** Format: Login-VerifyUserNameOnlyFails (e.g.) | |||
*** No spaces, no underscores, and prefix with the test area | |||
*Give meaningful names to variables. This will make it easier to maintain the test case in the longer run. | *Give meaningful names to variables. This will make it easier to maintain the test case in the longer run. | ||