Artifact: Test Script |
This artifact contains the step-by-step instructions that compose a test, enabling its run. Text scripts can take the form of either documented textual instructions that are manually followed, or computer-readable instructions that enable automated testing.
Domains: Test
Purpose
Test scripts implement a subset of required tests in an efficient and effective manner.
Relationships
Roles | Responsible: Tester | Modified By: Test Analyst Test Designer Tester
Tasks | Input To: Integrate and Create Build Structure the Test Implementation Analyze Test Failure Develop Test Run Tests | Output From: Develop Test Develop Test Cases Structure the Test Implementation
Description
Brief Outline | Each Test Script should consider various aspects of testing, including the following: The basic computer hardware requirements (for example, processors, memory storage, hard-disk storage, input/output, and interface devices) The basic underlying software environment (for example, operating system and basic productivity tools, such as e-mail and a calendar) Additional specialized input/output peripheral hardware (for example, bar-code scanners, receipt printers, cash draws, and sensor devices) The required software for the specialized input/output peripheral hardware (for example, drivers, and interface and gateway software) The minimal set of software tools necessary to facilitate test, evaluation, and diagnostic activities (for example, memory diagnostics, automated test execution, and so on) The required configuration settings of both hardware and software options (for example, video-display resolution, resource allocation, environment variables, and so on) The required pre-existing consumables (for example, populated data sets, receipt printer dockets, and so on)
Illustrations
Templates | Test Script
Tailoring
Impact of not having | Without this artifact, it is difficult to ensure that tests are run consistently so that results are repeatable and errors can be recreated. If you do not use a test script, it is more difficult to verify that errors were not caused because of the way tests were run.
Reasons for not needing | This artifact might not be required if the tests are simple or if testing is done on an informal basis. However, for this approach to be successful, testers must track their processes, as they might need to recreate a problem scenario. Alternatively, you can use automatic capture and playback tools to provide a record of testing.
Representation Options | Manual Test Scripts may be documented using some form of text document, spreadsheet, or table, or using a specialized test documentation support tool. Automated Test Scripts may be created (recorded) or automatically generated using test automation tools, programmed using a programming language, or any combination of these. The Test Scripts may be modified to include programming concepts, such as referencing common function libraries, using variables, loops, and branching to increase the efficiency, effectiveness, and resilience of the scripts. In certain cases, it will be appropriate to use automated Test Scripts as informal, transient resources, avoiding the effort and cost of maintaining them.
More Information
Checklists | Test Data Test Script
Guidelines | Maintaining Automated Test Suites Programming Automated Tests Test Suite
This program and the accompanying materials are made available under the Eclipse Public License V1.0, which accompanies this distribution. OpenUP Copyright © Copyright IBM Corp. 1987, 2009. All Rights Reserved. © Copyright ABC Corp. 2009. All Rights Reserved. Includes materials licensed from IBM and Eclipse. See IBM copyright and Eclipse copyright .