Test case |
In software engineering, a test case is a set of conditions or variables under which a tester will determine if a requirement upon an software application is partially or fully satisfied. It may take many test cases to determine that a requirement is fully satisfied. In order to fully test that all the requirements of an application are met, there must be at least one test case for each requirement unless a requirement has sub requirements. In that situation, each sub requirement must have at least one test case.
What characterises a test case is that there is a known input and an expected output , which is worked out before the test. The known input should test a Precondition and the expected output should test a Postcondition.
Under special circumstances, there could be a need to run the test, produce results - and a team of experts evaluate if the results can be considered as pass. This happens often on new products performance number determination. The first test is taken as the base line for subsequent test / product release cycles.
Written test cases include a description of the functionality to be tested taken from either the requirements or use cases, and the preparation required to ensure that the test can be conducted.
Test cases are usually collected into Test Suites.
A variation of test cases are most commonly used in acceptance testing. Acceptance testing is done by a group of end-users or clients of the system to ensure the developed system meets their requirements.
=See also=
*Software testing *Unit test *Test script *Test plan *Test Suite *Design by contract|
|