• Tester

• Tester

• Implement Tests

• Create Test Cases

• Create Test Cases

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.

• Test Case

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.

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.

• Test Case

• Testing Qualitative Requirements