Lecture 3 - Test Cases and Test Suites -> Quick Intro -> Test Case Structure -> Results Of The Test Case Execution
The problem with a test case having only the expected result is that this piece of information (expected result) alone might not be sufficient to perform the test case execution. In the case of a large bottle of Sapporo, we can just unzip the backpack and look inside. In the case of software, as a rule, we need an instruction on how to reach an actual result.
Here is another example.
In our last example (we’ll refer to it as “Test Case with Credit Card”), the expected result (ER) was preceded by steps that were supposed to give the test case executor an actual result (AR). These steps can be also called the “procedure“.
Here is an analogy for you:
– The procedure is a set of steps on a staircase.
– The expected result is a certain object we are supposed to find if we climb to the top of that staircase.
– The actual result is what we actually find when we reach the top of the staircase.