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:32, 9 February 2010
, 9 February 2010no edit summary
No edit summary |
No edit summary |
||
| Line 9: | Line 9: | ||
## Suite: suite_Collections.py ("suite" is required and standard; _Collections.py is whatever area you're writing it for) | ## Suite: suite_Collections.py ("suite" is required and standard; _Collections.py is whatever area you're writing it for) | ||
# Have the testcase reviewed by a peer, following these requirements | # Have the testcase reviewed by a peer, following these requirements | ||
# Comment briefly about the flow and aim of the testcase | # Comment briefly about the flow and aim of the testcase, as well as commenting inline | ||
# Store xpath variables at the top of the testcase, naming them in a unique and identifiable way | |||
# If you're using a regular expression, comment before using it for what you're looking | |||
= Some good practices = | = Some good practices = | ||
* It's best to check if you are logged in at the beginning of every test case. At the end of the test case, always logout. | * It's best to check if you are logged in at the beginning of every test case. At the end of the test case, always logout. | ||