In the previous post, we introduced the RIP (Reachability, Infection, Propagation) Model that we use for mapping failure to a fault. Today we give a definition for Test Case values. We will introduce you to software testing based on the remarkable book, Introduction To Software Testing by Paul Ammann and Jeff Offutt.
Are Test Cases Really Dead
You have probably read that there is no point in documenting every step of a test case into a document and concluded that test cases are obsolete. What input for this opinion is wrong? What if a test case is anything that helps you in testing activities? It could be an exploratory testing charter.
Test Case Values
Anyhow, testing activity needs input:
Test Case Values: The input values necessary to complete some execution of the software under test.
We first need to clarify what does it mean to complete an execution of the software under test. That execution could be short as adding two numbers, or long as completing the weather prediction for tomorrow. This defines the “size” of test case values.
Testers must be aware that those inputs are just part of the overall testing activity. For example, if our system under test communicates with other system under test, that system has its own test case values.
The system under test has many inputs that support its execution path.