Revision: 4657
Author: [email protected]
Date: Tue Mar 1 05:05:25 2011
Log: Removed the test suite structure part for now..
http://code.google.com/p/robotframework/source/detail?r=4657
Modified:
/wiki/TestStructure.wiki
=======================================
--- /wiki/TestStructure.wiki Tue Mar 1 05:02:00 2011
+++ /wiki/TestStructure.wiki Tue Mar 1 05:05:25 2011
@@ -1,10 +1,10 @@
-#summary Where should new keywords and tests go
+#summary Where should new keywords go
<wiki:toc max_depth="2" />
= Introduction =
-These are high level guidelines on how to structure your tests in terms of
where to add keywords and where to add new tests.
+These are high level guidelines of where to add keywords.
= Should my keyword be in this file or library or some shared resource
file? =
@@ -111,53 +111,3 @@
}}}
</td></tr>
</table>
-
-
-
-= In which suite should my test be? =
-
- * New case into a folder with 10 suite files. Which one to choose?
- * Should One file be for one team? One Feature? One Userstory?
- * Usually best structure comes from tests with same setup/teardown being
in the same file.
- * So look at setups/teardowns, if same = same suite!
- * Tags can be used for tagging features/teams/whatever you otherwise
would use filenames for
- * One suite file for 1-20 test cases. Preferably no more than 10.
-
- * If you have tests with very heavy setups and teardowns, they can be
made depend on each other
- * Generally should be avoided. Tests should be independent.
- * If needed, the tests should be in the same suite file
- * Never have long chains of dependent tests (max 4-5).
- * Consider verifying the status of the previous test using ${PREV TEST
STATUS} and ${PREV TEST NAME} variables.
-
-
-<table>
-<tr><th>`slow_tests.txt`</th><th>`slow_tests.py`</th></tr>
-<tr><td>
-{{{
-Heavy test 1
- Setup system
- Do a long heavy workflow
- Check system status is OK
-
-Second heavy test
- Setup system
- Do a long heavy workflow
- Second heavy workflow
- Check system status is OK
-}}}
-</td>
-<td>
-{{{
-Heavy test 1
- Setup system
- Do a long heavy workflow
- Check system status is OK
-
-Second heavy test
- Should Be Equal ${PREV TEST STATUS} PASS
- Should Be Equal ${PREV TEST NAME} Heavy Test 1
- Second heavy workflow
- Check system status is OK
-}}}
-</td></tr>
-</table>
