The Testing Process

Write the Scripts

The Traceability Matrix defines what has to be tested. There is usually one test script for each line in the TM. Each test script has an objective or goal, which is the purpose of the test. The objective usually starts with "To verify that..." and then continues with the wording from the line in the Traceability Matrix. For example, if the TM states "Mobile phone numbers can only be entered in the format 9999-999-999" then the goal of this script is "To verify that mobile phone numbers can only be entered in the format 9999-999-999".

Each test script, or test case, has one or more steps to be performed. In this example, the steps would include entering mobile phone numbers in various formats other than the one desired to prove that they are rejected with a diagnostic.

A test script has at least two columns: the action to be performed, and the result expected. Frequently, test scripts also have a column on the left with the step number, and one on the right to indicate if that step passed or failed.

If there are things that must be done before this script can be run, then these should be defined in a section titled "Prerequisites".

Test 127: To verify that mobile phone numbers can only be entered in the format 9999-999-999 Date: Tester: Prerequisites: . Step Action Expected Result Pass/Fail 1 Enter 1234-456-789 Number is accepted without a diagnostic.  . 2 Enter 123-456-7890 A diagnostic should be displayed. . 3 Enter 1 A diagnostic should be displayed.  . 4 Type a blank, then press the Enter key. A diagnostic should be displayed.  . Comments on this test: .

Obviously, on a large project, there could be hundreds or even thousands of test scripts. Organisation then becomes an issue, with 3-ring binders allocated for each sub-project.

As you write the scripts, keep in mind that they may be performed many times. Thus they should be written in such a way that they are re-usable. For example, if a script states that a certain customer number is created, then that same customer number should be deleted (either in this script or in a subsequent one) so that the identical actions can be followed later, without having to go through all the scripts and change customer numbers. This promotes a uniform approach and ultimately saves time.