Issue 148: Document guidelines for writing good test cases, organizing
data, etc.
http://code.google.com/p/robotframework/issues/detail?id=148
New issue report by laukpe:
Here's a list Janne and I presented in a training yesterday. We can use it
as a base.
* Every test must have an assertion
* A test tests only one thing
* multiple assertions are ok, but they should be related to same thing
* there should be clear case
* Tests should be independent, dependencies are managed with setup/teardown
* Test case names should remove need for test case documentation
* Test should be understandable without documentation
* Use domain language, correct and uniform abstarctions
* Use User Keywords to hide implementation details
* Limit the number of top level keywords max < 10
* Too many levels of abstarcation is not good either
* Always remember to handle clean up teardown
* Tests in one suite should be related to each other
* max ~8 tests, if not data-driven
* similar setup is a good indicateor
* Variables should be used to encapsulate long/complicated values
* No complex logic in test case level
* No For loops. if/else, or assignment to variable
* Setup/Teardwon should not be test cases
* Keywords in a resource file should relate to each other
Issue attributes:
Status: Accepted
Owner: ----
Labels: Target-ASAP Type-Documentation Priority-High
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
