Task: Create Test Cases |  |
Develop the test cases and test data for the requirements to be tested.
Disciplines: Test
Purpose
To achieve a shared understanding of the specific conditions that the solution must meet.
Relationships
Roles | Primary Performer: Tester | Additional Performers: Analyst Developer Stakeholder
Inputs | Mandatory: Use Case | Optional: Supporting Requirements Specification Test Case
Outputs | Test Case
Steps
Review the requirements to be tested
Work with Analyst and Developer to identify which scenarios need new or additional test cases. Review the Iteration Plan to ensure you understand the scope of development for the current iteration.
Identify relevant Test Cases
Identify paths through the scenario as unique test conditions. Consider alternative or exception paths from both a positive and negative perspective. Discuss the requirement with the Stakeholder to identify other conditions of satisfaction for the requirement. List the test cases with a unique name that identifies the condition they evaluate or their expected result.
Outline the Test Cases
For each test case, write a brief description with an expected result. Ensure that a casual reader can clearly understand the difference between test cases. Note the logical pre-conditions and post-conditions that apply to each test case. Optionally, outline steps for the test case. Verify that test cases meet the Checklist: Test Case guidelines. For more information on the test case, see Template: Test Case.
Identify test data needs
Review each test case and note where data input or output might be required. Identify the type, quantity, and uniqueness of the required data, and add these observations to the test case. Focus on articulating the data needed and not on creating specific data. For more information on test data selection, see Checklist: Test Case.
Share and evaluate the Test Cases
Walk through the test cases with the Analyst and Developer responsible for the related scenario. Ideally, the Stakeholder also participates. Ask the participants to agree that if these test cases pass, they will consider these requirements implemented. Elicit additional test ideas from the Role: Analyst and the Stakeholder to ensure you understand the expected behavior of the scenario. During the walkthrough, ensure that: The Use Cases and Supporting Requirements Specification planned for the current iteration have test cases. All the participants agree with the expected results of the test cases. There are no other conditions of satisfaction for the requirement being tested, which indicates either a missing test case or a missing requirement.
Key Considerations
Develop test cases in parallel with requirements so that Role: Analyst and Role: Stakeholder can agree with the specific conditions of satisfaction for each requirement. The test cases act as acceptance criteria by expanding on the intent of the system through actual scenarios of use. This allows team members to measure progress in terms of passing test cases.
This program and the accompanying materials are made available under the Eclipse Public License v1.0 which accompanies this distribution. OpenUP Copyright.