aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorBoris Kolpackov <boris@codesynthesis.com>2016-10-31 18:01:40 +0200
committerBoris Kolpackov <boris@codesynthesis.com>2016-11-04 09:26:36 +0200
commit1f7ab003ff8f14279ba69f9614e63b77bb35a8b6 (patch)
treeaab96451b5c7d36e86616666944737583f637ddb /doc
parentd55fcf77b0c8153f00c84d5d758a94a851cadda3 (diff)
Add clarification of combination tests to testscript spec
Diffstat (limited to 'doc')
-rw-r--r--doc/testscript.cli8
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/testscript.cli b/doc/testscript.cli
index 88d6609..e928d74 100644
--- a/doc/testscript.cli
+++ b/doc/testscript.cli
@@ -1402,6 +1402,14 @@ that real-world usage will uncover much more interesting interactions that you
would never have thought of yourself.To quote a famous physicist, \"\i{... the
imagination of nature is far, far greater than the imagination of man.}\"
+To expand on combination tests, don't confuse them with corner case tests. As
+an example, say you have tests for feature A and B. Now you wonder what if for
+some reason they don't work together. Note that you don't have a clear
+understanding of why they might not work together; you just want to add one
+more test, \i{for good measure}. We don't do that. To put it another way, for
+each test you should have a clear understanding of what logic in the code you
+are testing.
+
One approach that we found works well is to look at the changes you would like
to commit and make sure you have a test that exercises each \i{logic
branch}. It is also a good idea to keep testing in mind as you implement