QA/Execution/Web Testing/Selenium Guidelines: Difference between revisions

QA/Execution/Web Testing/Selenium Guidelines (view source)

65 bytes added , 9 February 2010

no edit summary

Confirmed users

9,511

edits

@@ Line 1: / Line 1: @@
 Here be some Selenium guidelines (mostly for writing, but include running here too).
+= Pre-checkin requirements =
+# Testcase/suite naming structure:
+## Give meaningful names to testcases
+## Don't use hyphens
+## Testcase: e.g.: collections_addNewCollection.py
+## Suite: suitename_Collections.py
+# Have the testcase reviewed by a peer, following these requirements
+# Comment briefly about the flow and aim of the testcase
 = 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.
-** 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.
-*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.
 Example: StoreElementpresent link=log in not_logged_in