QA/Execution/Web Testing/Docs/Automation/StyleGuide: Difference between revisions

QA/Execution/Web Testing/Docs/Automation/StyleGuide (view source)

237 bytes removed , 25 May 2011

Confirmed users

753

edits

@@ Line 86: / Line 86: @@
 *Module names should be called test_ and then behavioural areas. E.g. test_search_positive.py
-*Test setup should read in details from vars.py
+*Test setup should read in details from conftest.py
 *Test Case names should always show the intent of the test case.
@@ Line 92: / Line 92: @@
 <pre class="brush:py;toolbar:false;">
      # Good
-     def test_that_advanced_search_doesnt_find_item(self):
+     def test_that_advanced_search_doesnt_find_item(self, testsetup):
      # Bad
@@ Line 98: / Line 98: @@
 </pre>
-**CAVEAT: setUp and tearDown are exceptions to the rule as they are needed for unittest
 *Tests should handle the asserts not the Page objects
-*Every Test module will have an main() function caller
-<pre class="brush:py;toolbar:false;">
-        if __name__ == "__main__":
-            unittest.main()
-</pre>