Confirmed users
1,477
edits
QA/Execution/Web Testing/Selenium Guidelines: Difference between revisions
QA/Execution/Web Testing/Selenium Guidelines (view source)
Revision as of 00:05, 14 January 2010
, 14 January 2010→Some good practices
| Line 1: | Line 1: | ||
Here be some Selenium guidelines (mostly for writing, but include running here too). | Here be some Selenium guidelines (mostly for writing, but include running here too). | ||
=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. | ||
*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. | ||
*It's best to check if you are logged in at the beginning of every test case. | *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. | ||
Example: StoreElementpresent link=log in not_logged_in | |||
gotoIf ${not_logged_in}==true target | |||
clickAndWait link=Log out | |||
label target . . | |||
label target | |||
. | |||
. | |||
=IDE= | =IDE= | ||