Automated Testing Tools - Software Testing: Testing Across the Entire Software Development Life Cycle - page 162

11.3 TEST TOOL RECORD/PLAYBACK PARADIGM

Automated test tools that execute the application under test (AUT) are designed to be
used in a unique way. This unique way is referred to as “record/playback.” The term
is shorthand for the following repeatable three-step process.

Step 1. An end-user operates the AUT to accomplish some useful business task.
Step 2. The test tool “watches” the end-user operations and records/saves
the actions in a fi le of reusable commands called a script fi le.

Step 3. The test tool plays the script fi le back in order to precisely recreate the end-

user operations in the application without human intervention.

Figure 11.1 illustrates this unique record/playback paradigm.

Test computer
running the AUT

1. End-user
operates the AUT
(repeatable)

3. Test tool plays script
back (repeatable)

2. Test tool ''watches'' end-user
and records actions as a script
(repeatable)

Test tool
script file

Figure 11.1 Tets tool record/playback paradigm

The end-user provides the application intelligence to the test tool by operating
the AUT in a presumably correct manner. The test tool “looks over the end-user's
shoulder” and writes down what the end-user does. The test tool's recording of the
end-user operations is saved as some kind of command fi le, called a script fi le, for
later playback. At a later time, the tool can be directed to use this script fi le to cause
the AUT to operate exactly as if the end-user was sitting in the chair and operating it.
All three steps are designed to be repeatable and in fact are repeated many times
during the course of correct test tool usage. The end-user can operate the AUT for
many different business activities or for the same business activity many times as the
activity becomes more refi ned during the development process.
The test tool can be used to record and rerecord any end-user session. Rerecording
might be necessary because the end-user made a mistake in operation and needs to
repeat the operation. Rerecording might also be necessary because the previously
recorded operation has been changed during software development.