Intro Models Documentation Design Scripting Tools Execution Defects Reporting  

Test Scripting

Once the test cases have been derived and agreed the process of test scripting can begin. Test scripts are another implementation of the associated requirements, they can be manual or automated are as succeptible to error as code is. Most testing is carried out in teams and to ensure that all scripts are written in a consistent manner it is useful to set out a set of scripting standards, these are often included in the Test Plan.

Common components of scripting conventions are:

  • Test identifier
  • Issue
  • Author
  • Test Environment
  • Requirement Section
  • Status
  • Test Phase
  • Test Priority
  • Test Description
  • Test Step Number
  • Test Step Description
  • Test Step Expected Result

When writing test scripts it is vital to make them independent of assumed knowledge, it should be possible to hand a test script to any team member and expect them to run it unaided.

Reviewing Test Scripts

Perhaps the biggest contributor to high quality test scripts is the peer review or inspection. This invlolves a chair person, sometimes the test team leader, convening a group of testers to go through a draft test script, line by line, checking for quality and correctness. If you have a test scripting standards document this can be used as a checklist. Since the test script is an implementation of the requirements it is important that the cast of the review ensure that the tester's interpretation of the specification is correct.

All observations and corrections are recorded in a review form which acts as a list of corrective work for the script author. Once all corrections are made the test can be set to a reviewed status. The following is an example of a simple test script:

Test Identifier: TC01 Issue: 0.1
Author: John Elsen Status: Draft
Test Phase: System Test Test Priority: Medium
Requirement: Low Bal Handling 1.1.1
Test Description: Called party is a landline number, calling party has a zero balance
Step No. Step Description Expected Result
1. Set up a prepay subscriber Prepay subscriber is set up
2. Check the subscriber's balance Subscriber has a zero balance
3. Attempt to make a call to a landline number Subscriber receives insufficient balance announcement
4. Subscriber clears the call Call is cleared

Before we can consider executing tests we should review our test tool requirements.


Home      |      Testing      |      Telecoms      |      Resources      |      Clients      |      Contact     |     Care Database
 Copyright © 2016 Chic Computer Consultants. All rights reserved