Lecture 3 - Test Cases and Test Suites -> Quick Intro -> Test Case StructureBefore going on a fishing trip, Mr. Wilson came up with the following list:
1. Fishing pole
2. Box with extra hooks, fishing lines, and other gear
3. Can with worms
4. Huge beer mug
5. Large bottle of Sapporo
6. Potato chips
In the morning, trying not to wake up his wife, kids, two cats and the canary, Mr. Wilson takes that list and checks his backpack for the availability of each of the 6 objects.
Each item on his list is a test case.
The list itself is a test suite.
The process of figuring out and writing down each item is test case generation.
The process of checking the backpack for the availability of each object on the list is test case execution.
An essential part of the test case is the expected result-for instance, “Large bottle of Sapporo”. Thus, a test case can consist of only an expected result.
Please, note that today we’ll talk about formal side of test case; i.e., test case structure, useful attributes; formatting, etc. In future lectures, we’ll learn about actual side of test case; i.e., about test case content that would have high probability to find a bug. Next ->
Lecture 3 - Test Cases and Test Suites -> Quick Intro -> Test Case Structure
