Updating the test case document: Testcases

Test Cases contain the most detailed level of information in the Functional Verification Test Case Document. A Test Case is a collection of connected Use Cases, Procedures, Data, and Expected Results that describe a user flow through the system. In Test Cases, test Cases are grouped by Test Scenarios.

About this task

To design test cases, include the following test paths:

Valid input and output paths, which are based on test strategies and techniques.
Invalid and unexpected input and output paths.

If you decide not to run a test case, do not remove the test case from the test case document. References are used in the test plan and removing a test case might break the reference link. Hide, annotate, or strike through unneeded test cases.

A new Test Case can be added either a new test case table, or to an existing test case table. You add a test case to an existing test case table for the following reasons:

A new Use Case is added to an existing Test Scenario that introduces new Test Conditions
A new Test Case is added to increase Test Coverage
An existing Use Case is modified to introduce new Test Conditions and Values
Data is changed to create a Test Condition or Value

Procedure

New Test Case Table is added.

Option	Description
A template Test Case table exists	Use the existing template test case table. The test case document has a template test case table at the end. Using the conditions that are outlined in the Test Condition Matrix, determine the objectives of each test case and fill out the Test Objectives column. Using the Scenario to Use Case Mapping, determine the use cases and the steps that are involved in the scenario. By putting together the steps from the use cases, make a logical flow with the data conditions identified to form test case procedure. For each procedural step, enter the data values where applicable. Not all steps have data associated. When you enter data, refer to the Data tab and check whether the data is already defined in the data column. If the data is already defined in the Data tab, the data can be referenced in the test case. If the data is not already defined in the Data tab, it can be defined in the Data tab, and then referenced from the test case. For each procedural step, enter the expected results where applicable. Note that not all steps have expected results associated. Wireframes or HTML Mock-Ups can be referenced in the expected results if they are available. If the performed step results in a message or warning, it can be referenced from the Messages tab. Expected results must be written clearly so that the person who is running the tests can understand what to expect after each step.
A template Test Case table does not exit	Copy and paste the last test case table at the end of the Test Case tab Update the test scenario, objective, test condition matrix, and scenario use case map references to point to the appropriate places using the previous Test Case table as a sample. Update the test case name references to reference the test case names in the Test Condition Matrix using the previous Test Case table as a sample. Using the conditions that are outlined in the Test Condition Matrix, determine the objectives of each test case and fill out the Test Objectives column. Using the Scenario to Use Case Mapping, determine the use cases and the steps that are involved in the scenario. By putting together the steps from the use cases, make a logical flow with the data conditions identified to form test case procedure. For each procedural step, enter the data values where applicable. Not all steps have data associated. When you enter data, refer to the Data tab and check whether the data is already defined in the data column. If the data is already defined in the Data tab, the data can be referenced in the test case. If the data is not already defined in the Data tab, it can be defined in the Data tab, and then referenced from the test case. For each procedural step, enter the expected results where applicable. Note that not all steps have expected results associated. Wireframes or HTML Mock-Ups can be referenced in the expected results if they are available. If the performed step results in a message or warning, it can be referenced from the Messages tab. Expected results must be written clearly so that the person who is running the tests can understand what to expect after each step.

Option

Description

A template Test Case table exists

Use the existing template test case table. The test case document has a template test case table at the end.
Using the conditions that are outlined in the Test Condition Matrix, determine the objectives of each test case and fill out the Test Objectives column.
Using the Scenario to Use Case Mapping, determine the use cases and the steps that are involved in the scenario. By putting together the steps from the use cases, make a logical flow with the data conditions identified to form test case procedure.
For each procedural step, enter the data values where applicable. Not all steps have data associated. When you enter data, refer to the Data tab and check whether the data is already defined in the data column.
1. If the data is already defined in the Data tab, the data can be referenced in the test case.
2. If the data is not already defined in the Data tab, it can be defined in the Data tab, and then referenced from the test case.
For each procedural step, enter the expected results where applicable. Note that not all steps have expected results associated. Wireframes or HTML Mock-Ups can be referenced in the expected results if they are available. If the performed step results in a message or warning, it can be referenced from the Messages tab. Expected results must be written clearly so that the person who is running the tests can understand what to expect after each step.

A template Test Case table does not exit

Copy and paste the last test case table at the end of the Test Case tab
Update the test scenario, objective, test condition matrix, and scenario use case map references to point to the appropriate places using the previous Test Case table as a sample.
Update the test case name references to reference the test case names in the Test Condition Matrix using the previous Test Case table as a sample.
Using the conditions that are outlined in the Test Condition Matrix, determine the objectives of each test case and fill out the Test Objectives column.
Using the Scenario to Use Case Mapping, determine the use cases and the steps that are involved in the scenario. By putting together the steps from the use cases, make a logical flow with the data conditions identified to form test case procedure.
For each procedural step, enter the data values where applicable. Not all steps have data associated. When you enter data, refer to the Data tab and check whether the data is already defined in the data column.
1. If the data is already defined in the Data tab, the data can be referenced in the test case.
2. If the data is not already defined in the Data tab, it can be defined in the Data tab, and then referenced from the test case.
For each procedural step, enter the expected results where applicable. Note that not all steps have expected results associated. Wireframes or HTML Mock-Ups can be referenced in the expected results if they are available. If the performed step results in a message or warning, it can be referenced from the Messages tab. Expected results must be written clearly so that the person who is running the tests can understand what to expect after each step.

New Test Case is added to an existing Test Case table
To update:
1. Using the conditions that are outlined in the Test Condition Matrix, determine the objectives of each test case and fill out the Test Objectives column.
2. Using the Scenario to Use Case Mapping, determine the use cases and the steps that are involved in the scenario. By putting together the steps from the use cases, make a logical flow with the data conditions identified to form test case procedure.
3. For each procedural step, enter the data values where applicable. Not all steps have data associated. When you enter data, refer to the Data tab and check whether the data is already defined in the data column.
  1. If the data is already defined in the Data tab, the data can be referenced in the test case.
  2. If the data is not already defined in the Data tab, it can be defined in the Data tab, and then referenced from the test case.
4. For each procedural step, enter the expected results where applicable. Note that not all steps have expected results associated. Wireframes or HTML Mock-Ups can be referenced in the expected results if they are available. If the performed step results in a message or warning, it can be referenced from the Messages tab. Expected results must be written clearly so that the person who is running the tests can understand what to expect after each step.