Confirmed users
2,197
edits
QA/Execution/Web Testing/Docs/Automation/StyleGuide: Difference between revisions
Jump to navigation
Jump to search
QA/Execution/Web Testing/Docs/Automation/StyleGuide (view source)
Revision as of 16:16, 29 September 2011
, 29 September 2011→Test Style Guide
Teodosia.pop (talk | contribs) |
|||
| Line 79: | Line 79: | ||
</pre> | </pre> | ||
==Test Style Guide== | == Test Style Guide == | ||
* Module names should be called test_ and then behavioural areas. E.g. test_search_positive.py | |||
*Module names should be called test_ and then behavioural areas. E.g. test_search_positive.py | * Test setup should read in details from conftest.py | ||
* Test Case names should always show the intent of the test case. | |||
*Test setup should read in details from conftest.py | |||
*Test Case names should always show the intent of the test case. | |||
<pre class="brush:py;toolbar:false;"> | <pre class="brush:py;toolbar:false;"> | ||
# Good | # Good | ||
| Line 94: | Line 90: | ||
def test_advanced_search(self): | def test_advanced_search(self): | ||
</pre> | </pre> | ||
* Tests should handle the asserts not the Page objects | |||
*Tests should handle the asserts not the Page objects | |||
==Size of patches== | ==Size of patches== | ||
To make sure that we can review your patch as quickly and efficiently as possibly we would like patches to have 1 test in them and the necessary changes to the Page Objects. This also limits the chances of merge conflicts laters. | To make sure that we can review your patch as quickly and efficiently as possibly we would like patches to have 1 test in them and the necessary changes to the Page Objects. This also limits the chances of merge conflicts laters. | ||