Artifact: Test Case |  |
This artifact is the specification of a set of test inputs, execution conditions, and expected results, identified for the purpose of making an evaluation of some particular aspect of a scenario.
Domains: Test
Purpose
The purpose of this artifact is to: provide a way to capture test inputs, conditions, and expected results for a system systematically identify aspects of the software to test specify whether an expected result has been reached based on verification of a system requirement, set of requirements, or scenario
Relationships
Roles | Responsible: Tester | Modified By: Tester
Tasks | Input To: Implement Tests Create Test Cases | Output From: Create Test Cases
Description
Main Description | A test case specifies the conditions which need to be validated to enable an assessment of some particular aspects of the system under test. A test case is more formal than a test idea and usually takes the form of a specification. In less formal environments, test cases can be created by identifying a unique ID, name, associated test data, and expected results. Test cases may be derived from many sources but will usually include a subset of both the requirements (such as use cases, performance characteristics, reliability concerns) and other types of quality attributes. For more information on types of tests and their relationship to quality test attributes, see Concept: Testing Qualitative Requirements.
Illustrations
Templates | Test Case
Tailoring
Impact of not having | Without this artifact it is difficult to validate system functionality. Since this artifact is also often used to specify the conditions of acceptance between the stakeholders and the developers, it is more difficult to establish exit criteria and to demonstrate that the exit criteria have been met without it. It is also not possible to do regression testing if the original test cases have not been documented.
Reasons for not needing | It may not be necessary to create this artifact for maintenance or small enhancements to existing systems which will likely have existing test assets that can be utilized. Likewise package applications often come with their own set of test cases that would not require a separate instance of this artifact.
More Information
Checklists | Test Case
Concepts | Testing Qualitative Requirements
This program and the accompanying materials are made available under the Eclipse Public License v1.0 which accompanies this distribution. OpenUP Copyright.