SDLC - Specify Tests

Skip repetitive navigation links.

Specify Tests

The purpose of a test case is to specify and communicate the specific conditions that need to be validated in order to assess the target test items. A test case differs from a test idea, in that the test case is a more fully-formed specification of the test. Test cases may be motivated by many things but will usually include a subset of both the requirements (Use Cases , Business Rules , etc.) and the risks the project is concerned with.

A Test Case should include:

1. Test Case Description - the purpose or objective of the test, the scope, and any preconditions of the test.

2. Execution Condition - a description of a condition that will be exercised during the test.

Pre-Conditions - for each execution condition, describe the required state that the system should be in before the test can begin.

Test Inputs - for each execution condition, enumerate a list of the specific stimuli to be applied during the test. This is generally referred to as the "Inputs" to the test, and includes the objects or fields interacted with and the specific data values entered when executing the Test Case.

Observation Points - during the test execution, enumerate what specific observations should be made.

Control Points - during the test execution, identify any points where the flow of control may alter or vary.

Expected Results - the resulting state or observable conditions that are expected as a result of the test having been executed. Note that this may cover both positive and negative responses (such as error conditions and failures).

Post-Conditions - for each execution condition, describe the required state that the system should be returned to, allowing subsequent tests to be performed.

Refer to the Test Case template for more details.