Test Case Specification:

Test case is a well-documented procedure designed to test the functionality of the feature in the system.

For designing the test case, it needs to provide set of inputs and its corresponding expected outputs.

Parameters:

1. Test case ID: is the identification number given to each test case.

2. Purpose: defines why the case is being designed.

3. Precondition: for running in the system can be defined, if required, in the test case.

4. Input: should not hypothetical. Actual inputs must be provided, instead of general inputs.

Using the test plan as the basis, the testing team designs test case specification, which then becomes the basis for preparing individual test cases. Hence, a test case specification should clearly identify,

1. The purpose of the test: This lists what features or part the test is intended for.

2. Items being tested, along with their version/release numbers as appropriate.

3. Environment that needs to be set up for running the test cases: This includes the hardware environment setup, supporting software environment setup, setup of the product under test.

4. Input data to be used for the test case: The choice of input data will be dependent on the test case itself and the technique followed in the test case.

5. Steps to be followed to execute the test: If automated testing is used, then, these steps ate translated to the scripting language of the tool.

6. The expected results that are considered to be “correct result”.

7. A step to compare the actual result produced with the expected result: This step should do an “intelligent” comparison of the expected and actual results to highlight any discrepancies.

8. Any relationship between this test and other test: These can be in the form of dependencies among the tests or the possibilities of reuse across the tests.