TestTrak (tm) Lite V1.1
An automated testing system designed to
simplify and accelerate QA testing of text
based applications. Can be used to test PC
software and hardware. Records keystrokes
and screens. Allows single step playback
and comparison or automated batch playback.
Can also be used to automate PC processes.
Shareware ($55) from Syscon, Inc.

TestTrak (tm) Lite User Manual
Version 1.1
October 25, 1992






Syscon ,Incorporated
96 Frederick St, Unit 60
Dracut, MA 01826

Phone: (508) 957-6661
FAX: (508) 957-3263
Compuserve: 71371,3410


Copyright: Copyright 1991 by Syscon, Incorporated. All rights
reserved worldwide.

Trademarks: TestTrak is a trademark of TestTrak Partners.

Disclaimer: Syscon, Incorporated makes no representation or
warranties of any kind with respect to the contents hereof and
specifically disclaims any implied warranties of merchantability of
fitness for any particular purpose. Further, Syscon Incorporated
shall not be liable for errors which may be contained herein or for
incidental or consequential damages arising in connection with the
furnishing, performance, or use of this manual. Syscon,
Incorporated reserves the right to revise this manual from time to
time and to make changes in the contents hereof without obligation
to notify any person of such revision or change.



Contents

Introducing TestTrak Lite . . . . . . . . . . . . . . . . . . . . . . 1
Features and Benefits. . . . . . . . . . . . . . . . . . . . . . 1
Considerations and Restrictions. . . . . . . . . . . . . . . . . 2

Using This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . 5
About This Manual. . . . . . . . . . . . . . . . . . . . . . . . 5
Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Getting Around in TestTrak for Text. . . . . . . . . . . . . . . 6
Menus. . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Components in Screens and Dialog Boxes . . . . . . . . . . 7
Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Chapter 1: Getting Started. . . . . . . . . . . . . . . . . . . . . . 9
Before You Start . . . . . . . . . . . . . . . . . . . . . . . . 9
Assumptions. . . . . . . . . . . . . . . . . . . . . . . . 9
Check the README.BAT File. . . . . . . . . . . . . . . . . . . . 10
Installing TestTrak. . . . . . . . . . . . . . . . . . . . . . . 11
Where to Go From Here. . . . . . . . . . . . . . . . . . . . . . 11

Chapter 2: About Automated Testing. . . . . . . . . . . . . . . . . . 13
About Testing. . . . . . . . . . . . . . . . . . . . . . . . . . 13
Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Test Conditions. . . . . . . . . . . . . . . . . . . . . . 14
Drafting Your Test Plan. . . . . . . . . . . . . . . . . . 15

Chapter 3: Using TestTrak for Text. . . . . . . . . . . . . . . . . . 17
Using TestTrak to Test PC Software Applications. . . . . . . . . 17
Creating a Test Data Script. . . . . . . . . . . . . . . . 17
Playing Back Your Test Data Scripts. . . . . . . . . . . . 18
Putting Data Files Into Batch Files. . . . . . . . . . . . 19
Modifying Existing Test Data Scripts . . . . . . . . . . . 19
Debugging Errors in Regression Tests . . . . . . . . . . . 19
Using TestTrak to Test PC BIOS and Hardware. . . . . . . . . . . 21
Using TestTrak to Test Mainframe/UNIX Software . . . . . . . . . 23

Chapter 4: Recording Test Data Scripts. . . . . . . . . . . . . . . . 25
Starting Record Mode . . . . . . . . . . . . . . . . . . . . . . 25
Entering Test Data Script Filename . . . . . . . . . . . . . . . 26
Capturing Screens and other Special Operations . . . . . . . . . 28
Capture Screen . . . . . . . . . . . . . . . . . . . . . . 29
Capture Palette. . . . . . . . . . . . . . . . . . . . . . 30
Exit Recording . . . . . . . . . . . . . . . . . . . . . . 30
Suspend Recording. . . . . . . . . . . . . . . . . . . . . 31
Resume Recording . . . . . . . . . . . . . . . . . . . . . 31
Time Delay . . . . . . . . . . . . . . . . . . . . . . . . 31
Warm Boot. . . . . . . . . . . . . . . . . . . . . . . . . 31
Reset Timer. . . . . . . . . . . . . . . . . . . . . . . . 31
Setting the Hotkey . . . . . . . . . . . . . . . . . . . . . . . 32

Chapter 5: Playing Back Test Scripts. . . . . . . . . . . . . . . . . 33
Starting Playback Mode . . . . . . . . . . . . . . . . . . . . . 33
Data File Playback . . . . . . . . . . . . . . . . . . . . . . . 34
Batch File Playback. . . . . . . . . . . . . . . . . . . . . . . 36
Set Playback Speed . . . . . . . . . . . . . . . . . . . . . . . 38
Set Attribute Checking . . . . . . . . . . . . . . . . . . . . . 39

Chapter 6: Debugging Test Data Scripts. . . . . . . . . . . . . . . . 41
Starting Debug Mode. . . . . . . . . . . . . . . . . . . . . . . 41
Run Until Error Debug. . . . . . . . . . . . . . . . . . . . . . 43
Single Step Debug. . . . . . . . . . . . . . . . . . . . . . . . 44

Chapter 7: Using the TestTrak Batch File Editor . . . . . . . . . . . 47
Batch File Editor. . . . . . . . . . . . . . . . . . . . . . . . 47
Edit Batch File. . . . . . . . . . . . . . . . . . . . . . . . . 47

Chapter 8: Using the TestTrak Data File Editor. . . . . . . . . . . . 51
Introduction To the Data File Editor . . . . . . . . . . . . . . 51
Getting Around in the Data File Editor . . . . . . . . . . . . . 52
Starting the TestTrak Data File Editor . . . . . . . . . . . . . 53
Data . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
File . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Special. . . . . . . . . . . . . . . . . . . . . . . . . . 61
Using the TestTrak Editor. . . . . . . . . . . . . . . . . . . . 62



Introducing TestTrak LiteTM

TestTrakTM Lite for Text is an automated testing program that is
designed to simplify and accelerate QA testing of character-based
applications. It can be used to test PC based software, hardware
or mainframe software. Once a test script has been created you can
run it automatically again and again, using the computer itself to
check the integrity of your application. If the software you're
testing changes, you can easily modify your scripts to accommodate
those changes, thereby saving time and money.



Features and Benefits

The features and benefits of TestTrak Lite include:

o Minimal Size. The resident portion of TestTrak Lite requires
less than 30K of DOS conventional memory.

o User Friendly. Menu bars and popups provide an intuitive
interface. Context sensitive help screens are provided.

o Editor. Lets you create and modify test scripts
independently of your application. So you can begin test
development before your application development is
finished.

o User-independent Regression Testing. Once test data scripts
have been completed successfully, you can run them
without having to be there. For example, you can start
the regression test at night, and come in the next
morning and check the results.

o Keystroke Timing Recorded. In addition to recording the
keystrokes themselves, TestTrak also records the exact
time between each keystroke. Thus when you play back the
script it will be at exactly the rate it was recorded.
Some programs, particularly mainframe programs will not
work correctly when played back without this capability.

o Variable Playback Speed. This option enables you to set the
speed at which you want a file played back. This allows
you to run test scripts for software applications that
are not time-dependent very quickly.

o Screen masking. The Capture Screen option allows you to
mask parts of screens that you do not want captured as
part of your test. For example, if you do not want to
capture the time or date fields of a screen, you can
block them out and capture the rest of the screen.

o Warm boot. TestTrak lets you insert a warm boot as part of
a test data script. This helps you test device drivers
with different command line configurations.

o Application debugging. The Debug option lets you debug your
software application while you test it. You can either
run the test until it hits an error, or you can do
single-step debugging.



Considerations and Restrictions

This section presents certain restrictions as well as
considerations that you need to be aware of before you begin to use
TestTrak for Text.

o Always start TestTrak at the DOS prompt, with a clear screen.
This enables you to start your test from a repeatable state,
as mentioned in Chapter 2, "About Automated Testing."

o While developing your test under TestTrak, it is important
that you watch the test to make sure the application being
tested is doing what it should be. Only the tester can
determine the correctness of the application during the test
development. TestTrak only checks for errors when you are
playing back a developed test data script.

o If you are testing something that requires you to modify
CONFIG.SYS, such as a device driver that can be loaded at
different addresses, you can record a warm boot (CTRL + ALT +
DELETE) as part of your test.

o If you are testing a mainframe application, the first thing
the test must do is bring up the terminal emulator that the
mainframe application will communicate with.

o You can use any text editor to edit the batch files. To
display or edit data files, you must use either the TestTrak
data file editor or TestTrak Modify mode.

o TestTrak will not capture mouse movements.

o TestTrak can be used to capture keystrokes in some graphics
applications but it cannot be used to record graphics screens.

o TestTrak cannot be used to test Microsoft Windows
applications.

o TestTrak captures keystrokes using INT 16, so any application
that activates hot keys by using hot keys from INT 9 (such as
TSRs) cannot be tested.



Using This Manual


About This Manual

This manual includes the following chapters.

o Chapter 1, "Getting Started," provides detailed installation
instructions.

o Chapter 2, "About Automated Testing," explains what automated
testing is, what the advantages of using it are, how to
prepare your test scripts, and the types of information you
need to be concerned with.

o Chapter 3, "Using TestTrak for Text," briefly describes the
types of things you can test, including PC software
applications, PC BIOS and hardware, and mainframe software
applications.

o Chapter 4, "Recording Test Data Scripts," describes how to use
TestTrak to create test data scripts.

o Chapter 5, "Playing Back Test Scripts," describes how to use
TestTrak to playback test data scripts, batch data scripts,
edit test batch scripts and alter the playback speed.

o Chapter 6, "Debugging Test Data Scripts," describes how to use
TestTrak to display comparison errors and test data script
keystrokes on the screen.

o Chapter 7, "Using the TestTrak Batch File Editor," describes
how to use the TestTrak batch file editor. This editor (or any
ASCII text editor) is used to create list of test data scripts
to be executed. The test data scripts are executed in the
order they appear in the ASCII batch file.

o Chapter 8, "Using the TestTrak Data File Editor," describes
how to use the TestTrak data script editor.


Conventions

This section explains the conventions that are used throughout this
manual. By taking a few minutes to read this section, you'll be
able to use this manual more effectively.

The term "select" is used when referring to selecting a menu option
or a file from a pick box.

The term "directory" is used when referring to a directory on a
disk, including any and all subdirectories. Whenever the directory
is displayed in a dialog box, you can change directories by
pressing F2 and entering the name of the new directory.

Three types of menus are used in TestTrak for Text: menu bars,
pull-down menus, and popup menus.

The HELP option provides additional menu-bar-specific information
about the options on the menu bar.

Exit or Quit always take you back to the previous operation.

Many TestTrak operations require you to enter information into a
dialog box.

Messages and prompts are displayed in popup boxes. Information
that you must enter is entered into entry boxes.

The arrow keys let you move around menus and pick boxes.


Getting Around in TestTrak for Text

This section explains how to use the menus and certain keys to get
around in TestTrak for Text. Although the TestTrak interface is
easy to use, you need to know how to get around the program before
you can use it.

This section explains how to:

o select menu options

o access popup menus

o use pick boxes and entry boxes

o use dialog boxes


Menus

Three types of menus are used in TestTrak for Text: menu bars,
pull-down menus, and popup menus. Menu bars are used for all main
menus in both the testing portion of TestTrak and in the TestTrak
Editor. In the testing portion of TestTrak, however, all submenus
are either pull-down menus or popup menus. In TestTrak Editor,
almost all menus are displayed as menu bars. Popup menus can be
accessed by typing CTRL-SHIFT-T (or the current hotkey).

You can select a menu item by moving the cursor to it and pressing
ENTER, or by typing the highlighted letter in that option.
Likewise, you can select a file from a pick box by moving the
cursor to it and pressing RETURN, or by typing the name of the file
and pressing ENTER.


Components in Screens and Dialog Boxes

When you select certain menu options, a screen or dialog box is
displayed. The screen or dialog box generally requires some input
from you, such as a file name; or they require you to select a file
or menu option before you can proceed. The following screen
includes a menu bar, entry box, pick box, and menu options.



Record Playback Debug Modify Editor Quit

Data File Playback
Batch File Playback

Current Directory: J:\SYSCON\TESTRACK

File Name
DUMB.TTD
TEST.TTD
WP51.TTD
REBOOT.TTD
SCRCAP.TTD BEGIN CANCEL
SIZE.TTD
SCRCAP2.TTD
EDITOR.TTD
TEST1.TTD
SPECIAL.TTD First enter the file name. Then select
either begin or cancel. You can exit at
any point by pressing Esc.

F1 - Help F2 - Change Directory F3 - Swap Boxes Esc - Exit


F1 - Help TestTrak v1.00 Copyright (c) 1991 TestTrak Partners



This screen requires that you enter the name of a file in the entry
box, or select an existing file name from the pick box. You can
then select either BEGIN to continue, or CANCEL to back out of the
operation.


To enter a file name in the entry box, type the name (the default
extension .ttd will be added automatically ) and press ENTER. The
cursor moves to BEGIN.

To select a file from the pick box, use the up or down arrow, PgUp,
or PgDn key to highlight the file name you want to select and press
ENTER. The cursor moves to BEGIN button.

If you want to enter a file name directly, press F3 to move the
cursor to the file entry box, enter the filename (including path if
necessary) of the test script you want to run and press ENTER. The
cursor will move to the BEGIN button.

Press ENTER to proceed at the BEGIN button, or use the right arrow
key to move the cursor to CANCEL and press ENTER to stop the
process.


Getting Help

TestTrak for Text provides a comprehensive online help system that
explains the program's options while you work. Most menu bars have
a HELP option that provides information that is specific to that
menu bar. For menu bars that do not have a HELP option, you can
press F1 for help.

You can move around the Help screens using the arrow keys, PgDn, or
PgUp.



Chapter 1: Getting Started


Before You Start

Before you install TestTrak for Text, you need to complete the
preliminary steps in this section. You should

o take note of the assumptions used in this manual

o check the software and hardware requirements

o fill out your registration card

o check your package and disk contents


You should read all the information in this section and complete
the necessary steps. They are essential to the proper operation of
TestTrak for Text.


Assumptions

The instructions in this manual assume you are familiar with basic
DOS commands (Microsoft or IBM PC disk operating System), including
formatting disks, erasing files, copying files, backing up files,
specifying a path name, and managing directories. If you are not
familiar with these terms and operations, refer to your DOS User's
Manual to learn about DOS before using TestTrak for Text.


What You Need

You need the following software and hardware to run TestTrak for
Text.

o Computer: an IBM PC, XT, AT or PS/2 computer (or a computer
that is 100% compatible with any of these).

o Memory: at least 256K of available RAM.

o Operating System: PC-DOS or MS-DOS, version 3.0 or later.

o Disk Drives: at least one floppy-disk drive and one hard-
disk drive.

o Display: A monochrome monitor with a monochrome display
adaptor; a composite monitor with a Color Graphics
Adapter; an Enhanced Color Display with an Enhanced
Graphics Adapter; a Video Graphics Adaptor and
monitor; or a monitor and display adapter
compatible with any of these.



Check Your Package Contents

Your TestTrak for Text package contains these items:

o TestTrak for Text User's Manual

o one 5.25-inch disk

o one 3.5-inch disk

o Registration Card


If any of these items is missing, contact Syscon, Inc., for a
replacement.


Check the README.BAT File

The README.BAT file contains information about TestTrak for Text
that became available after the user manual was printed. This
information is essential for using TestTrak for Text; please read
it before using this program.

You can read the contents of the README.BAT file by typing README
at the DOS prompt. Press return to display the next page after you
have finished reading each page. You can print the README file by
redirecting it to your printer with the following DOS command:
type readme.bat > prn.


Installing TestTrak

Note: Be sure to fill out the Registration Card that came in the
TestTrak package and return it to Syscon, Incorporated. You must do
this in order to receive technical support and to receive
information about updates. Please fill out the card, then send it
to Syscon.

The following procedure will make a backup copy of TestTrak and
install TestTrak on your hard drive.

1. Make a backup copy of all TestTrak Program disks using the DOS
diskcopy command. Use these backup copies to install the
TestTrak program. Store the original TestTrak diskettes in a
safe place.

2. Insert the backup TestTrak Program disk in drive A.

3. Type a:install at the A> prompt and then press ENTER.

4. Follow the instructions that appear on the screen. You can
install the TestTrak program on any hard disk in your system.

TestTrak is now installed onto your hard drive.



Where to Go From Here

Before you try to use TestTrak for Text, please read Chapter 2,
"About Automated Testing." That chapter provides essential
information for making maximum use of TestTrak's capabilities.
Chapter 2: About Automated Testing

This section provides a generic discussion of automated testing:
how it works, how to use it, and the advantages of using it.

Automated testing speeds up the process of QA testing by allowing
you to capture keystrokes, full or partial screens, warm boots, and
other operations and store them in a test data script in a file
that can be played back whenever necessary. The file can be
edited, put into a batch file, and used again and again.

This presents the user with significant savings in time and money
because the need to re-enter test data and re-verify the results
manually is eliminated. All you need to do is rerun the test
scripts. There is no need for you to watch the test or to manually
reenter keystrokes or other operations.




About Testing

When testing a software application (or BIOS or hardware), you are
testing it to make sure that it does what it is supposed to do, and
that it does not do what it is not supposed to do. In other words,
you want to find errors, not avoid them. And, because you want to
find errors, it is usually best if someone other than the developer
tests the application.

When writing test scripts for automated testing, you want to break
your test data scripts into small portions. This enhances the
repeatability or your scripts, and saves you time because if you
need to make a change to a script, you can go right to that
particular script and make a change. You do not have to redo the
entire test. These small test portions should contain all
necessary keystrokes/operations for one function.

In addition, all test data scripts should be independent of each
other. This also enhances the repeatability of the scripts and
allows you to use the scripts in different tests.

You should also make sure that each script starts at a known place
in the application and ends in a known place. This lessens the
possibility of errors and increases the repeatability of the
script.


Planning

When designing your automated test plan, you must consider the
conditions under which the test is to be run and which resources
will be involved. You can then draft a test plan that incorporates
the information determined in each of these processes. This
section discusses the types of information that need to be included
in the test plan, as well as suggestions for writing the test plan
in order to make maximum use of automated testing's capabilities.


Test Conditions

When determining how you will test your application, you must
consider any condition that will affect your test scripts. These
conditions can include

o The type of monitor you are using (VGA, EGA, etc.)

o The version of the software application you are testing

o Did the software have to be installed? If so, you should
consider incorporating the installation procedures into your
test plan.

o If you are testing a mainframe application, what emulator are
you using? Is it the same one you will use to test the
application in the future? The same one under which the
application will run?

o Are the conditions under which you are testing repeatable? In
other words, when you test the next version of the
application, will the same conditions that exist now be
present then?


Drafting Your Test Plan

Drafting your test plan is where you make maximum usage of
automated testing's capabilities. Because you want to write a test
plan that finds errors, is important to define those parts of the
application where errors are likely to be found. In addition,
because you want to be able to use the batch files that you create
again, it is important that each test script be defined in such a
way that you always start from a known place and always end up in
a known place. So, when defining your test scripts, keep these
questions in mind:

o Where does it start?
o Where does it end?
o Are the results repeatable?
o Are the test data scripts small enough so that changes in the
application require you to modify only a small number of the
test data scripts?

It is important to break your test scripts into small enough
portions so that each one tests a particular function. By doing
this, if there is a small change in the application, such as a
change in the user interface, you do not have to reenter the entire
sequence of the test. You can go to the test script in which the
change occurs and modify only that script. This keeps having to
modify test data scripts to a minimum.

When defining your test scripts, it is also important to keep the
concept of "boundary testing" in mind. Boundary testing enables
you to define those parts of an application where things are likely
to break, or where errors are most likely to occur. For example,
if you are testing a database that accepts a maximum of 100
entries, you might want to make one of the boundaries of a test
script the point at which you try to make 101 entries.
Chapter 3: Using TestTrak for Text

There are three types of places you might use TestTrak for Text:
testing PC software applications, testing PC BIOS and hardware, and
testing mainframe/UNIX software applications.

This section provides general information on using TestTrak for
Text to perform these three types of tests. It also provides some
examples of tests to give you a better idea of how you can use
TestTrak's capabilities. For more detailed information on using
TestTrak, refer to the following chapters.


Using TestTrak to Test PC Software Applications

This section discusses the steps that you would perform to create
a test data script, play back the script, put the data files into
a batch file, modify an existing script, and debug errors during
regression testing.

When you use TestTrak to test a software application that is
running on your PC, remember to keep your scripts as short as
possible to keep editing and modifying time to a minimum. And, to
reduce the possibility of errors in your scripts, keep the
repeatability factor in mind. Your scripts should start and end at
repeatable screens, and always be aware of which monitor you are
creating the test under. Tests developed on color monitors may not
run correctly against monochrome monitors, because some application
programs put up different attributes for characters in color.


Creating a Test Data Script

This section discusses the general steps you perform when creating
a test data script. For more detailed information on recording a
test data script, refer to Chapter 4, Recording Test Data Scripts.

When creating the test data script, do not assume that the
application you are testing is bug-free. It is important that you
watch the application to make sure that it does what you expect it
to. If it doesn't, you need to inform the application developers
so they can fix the problem. Then, you need to modify your test
data script. (A good way to help the developers recreate the
problem is to stop recording the script, give it to the developers,
and let them play the script back.)

When you start to record, you immediately go back to the DOS prompt
for the TESTTRAK directory.

1. Go into the application that you want to test. It is
important that you enter the entire, correct path for
accessing the application. Once again, this is important for
being able to repeat your test.

2. When you come to a screen that you want to capture, make sure
that the screen is repeatable. Then, press SHIFT-CTRL-T. The
Record popup menu is displayed.

3. Choose whether you want to capture the entire screen or a
portion of it. To capture only part of a screen, use the
Enable Screen and Disable Screen options.

4. Continue creating your test data script. Remember to keep it
as short as possible. Each script should perform one
function.

5. If you choose to insert a warm boot, do not add any keystrokes
or operations after the warm boot. Remember, when you are
playing the test script back, the warm boot will be performed
and no further steps can be performed. As before, this has to
do with the repeatability of the test data script.

6. When you are through with your test data script, go to the DOS
prompt and stop recording. Going to the DOS prompt means that
each script starts and ends at a known point, insuring your
script's repeatability.

7. When your script is complete, play it back to make sure that
it does what it is supposed to do. Note: You should do this
after each script to ensure that it is repeatable and that it
does not have any errors.

8. Then, go back into TestTrak and repeat these steps to record
your next test data script.

Make sure you keep a record of the names of your test data script
files so that you can put them into a batch file. You must enter
them in the order in which you want them played back.



Playing Back Your Test Data Scripts

The TestTrak for Text online Playback option allows you to play
back your data files immediately after you create them. You can
play them back in either single file mode (Data File Playback) or
batch mode (Batch File Playback).

When playing back a test data script for the first time, it is not
necessary for you to watch the playback. Any errors that occur
will be put into a log file with the extension and you can use the
Modify option or TestTrak Editor to correct them.

You should play back your data files first in single file mode so
that you can correct each file, if necessary. Then, you can put
the files into a batch file in the correct order and play them back
without any manual intervention. This is a time-saving feature
during regression testing because you can run the entire test suite
without having to be there. Any errors in your script are put into
the log file with the extension . You can use the Modify option or
TestTrak Editor to correct these errors. Or, if you want to watch
the errors as they occur, you can use the Debug option and correct
the software application as the errors as they occur.

The Playback option is also a good way to check the repeatability
of your test data scripts. For example, a test that is successful
in single file mode may not be successful in batch mode because the
screens are not repeatable when played together.

For more detailed instructions on using the Playback option, refer
to Chapter 5, Playing Back Test Scripts.



Putting Data Files Into Batch Files

To put a data file into a batch file, use the Edit Batch File
option from the Playback Menu. When the Edit Batch File screen is
displayed, enter the names of the data files you want included in
the file in the order in which you want them played back.


Modifying Existing Test Data Scripts

You can modify a test data script using either the online Modify
option or the TestTrak Editor. (If you do your modifications in
the TestTrak Editor, you will still have to use the online Modify
option for screen captures, timing between keystrokes, or time
delays.)



Debugging Errors in Regression Tests

The TestTrak online Debug option is for QA personnel who want to
put a little more detail in the problem report or who want more
help in finding errors in an application. Debug is also a good
tool for engineers who are debugging an application problem.

There are two ways to use TestTrak to detect errors: Run Until
Error and Single Step Debug.

Run Until Error plays back the file until it finds a screen that
miscompares. The screen is displayed with the areas that
miscompare highlighted and flashing. The screen is displayed until
you press the space bar. TestTrak continues playing back the file
until it encounters another screen miscompare.

Single Step Debug allows you to display the keystrokes that were
entered so you can see how you got from screen to screen. This is
a helpful feature if the person doing the debugging is not the same
person who created the test data script.

For more detailed information on using Debug, refer to Chapter 6,
Debugging Test Data Scripts.


Using TestTrak to Test PC BIOS and Hardware

Using TestTrak to test PC BIOS or hardware requires an extensive
knowledge of the IBM PC. If you have the required expertise, you
can test PC BIOS, or the motherboard hardware or option board
hardware/BIOS by using the DOS Debug program or other short
application programs that you have written to display the state of
hardware registers on the screen.

The following example tests the INT 10 Function 0 - Set Video Mode.
This example uses the ability of the DOS Debug program that is
supplied with all DOS versions to write and execute assembly
language programs. Start TestTrak and select Start Recording. When
you are back at the DOS prompt do the following:

Example:

1. Start the DOS program Debug and enter the following assembly-
language instructions to set the video mode to a 40-column x
25-line screen:

mov ax, 01
int 10
ret

2. Execute the program using the instructions g=100 105 then exit
DOS Debug.

3. Do a CLS command at the DOS prompt to clear the screen. (This
ensures that the screen is repeatable.)

4. Go back into DOS Debug and, at the Debug prompt, enter the
command:

d 40:49 L1

The memory byte that DOS uses to hold the current video mode
should now appear on the screen, and the value of that byte
should be 1.

5. Save the screen for comparisons in regression testing.

6. Enter another command at the Debug prompt:

d 40:4A L1

The memory byte that DOS uses to hold the number of columns on
the screen should appear and should be 50 hex (80 decimal).


7. Save the screen for comparisons in regression testing.

8. Exit DOS Debug mode and stop recording.

You can repeat these steps with each video mode that the system
has. You could then batch the steps together to create a test of
all the BIOS video modes.

Note: For further information on IBM PC hardware and BIOS, refer
to the IBM Technical Reference Manuals for PS/2 and the IBM ROM
BIOS Programmer's Reference, by Ray Duncan (Microsoft Press).


Using TestTrak to Test Mainframe/UNIX Software

Using TestTrak for Text to test mainframe/UNIX software
applications is very similar to the way you use it to test PC
software applications. In other words, you are still capturing
keystrokes and screens, and you can still use the TestTrak Editor
to create test data files without running the software application.
And, as with testing PC software applications, the same
considerations for shortness of scripts and repeatability of
testing conditions still apply.

When testing mainframe/UNIX software, however, there are some
additional caveats. For example, since you are logging on from a
remote site, you must run TestTrak under a terminal emulator. Make
sure that the emulator you test the application under is the same
one that you created the test under. Otherwise, the test may not
work.



In addition, you must be aware of timing and response times since
you are attaching to a remote site. For example, if you create a
test at a time when there is minimal traffic, at night for
instance, but run the test during the day when traffic is heavy,
the response times will differ and the test may not work.

If this is the case, you can use TestTrak's Time Delay feature to
insert a certain amount of time between keystrokes or operations.
(It doesn't matter if the response time is quicker, only if it's
slower.) In this way, you can manipulate your test data scripts to
increase the probability of a successful test.
Chapter 4: Recording Test Data Scripts

This section describes how to start TestTrak, and how to use its
menu options and capabilities to record test data scripts. Record
mode can only be used to create completely new test scripts. If you
want to modify an existing test script use Modify mode.


Starting Record Mode

To start record mode from your hard disk

1. Go into the directory in which you installed TestTrak.

2. Type testtrak and press ENTER. The TestTrak Main Menu
appears, as shown in Figure 4-1.


Record Playback Debug Modify Editor Quit



















F1 - Help TestTrak v1.00 Copyright (c) 1991 TestTrak Partners



. . . . . . . . . . .Figure 4-1. TestTrak Main Menu


3. Select record mode by using the arrow keys to move the cursor
to the record mode selection and pressing ENTER, or by typing
"R". The Record selections menu will appear as show in Figure
4.2. There are two selections:

o Start Recording
This selection is used to start a recording
session.

o Set Hotkey
This selection lets you change the key that is used
to display the option popup while you are
recording.



Record Playback Debug Modify Editors Quit

Start Recording
Set Hotkey


















F1 - Help TestTrak v1.00 Copyright (c) 1991 TestTrak Partners



. . . . . . . . . . . Figure 4-2. Record Main Menu


Entering Test Data Script Filename

Record mode allows you to create a test data script by recording
the keystrokes, capturing a full or partial screen, or performing
any other operations necessary to complete a test data script.
Before you start, please be sure you have read Chapter 2, About
Automated Testing.



To use Record mode,

1. From the TestTrak Record Menu, select START RECORDING. The
Record Mode screen is displayed, as shown in Figure 4-3.



Record Playback Debug Modify Editor Quit



Current Directory: J:\SYSCON\TESTRACK

File Name




BEGIN CANCEL




First enter the file name. Then select either
begin or cancel. You can exit at any time by
pressing Esc.

F1 - Help F2 - Change Directory Esc - Exit



F1 - Help TestTrak v1.00 Copyright (c) 1991 TestTrak Partners



. . . . . . . . . . .Figure 4-3. Record Mode Screen


The current directory is listed at the top of the dialog box.
This is the directory in which the test data script that you
are creating will be stored. To store the test data script in
another directory, press F2 and enter the name of the
directory you wish.

2. Enter the a new file name and press ENTER. (All file names
will be given the extension .ttd automatically to mark them as
TestTrak data scripts.)

If you enter an existing file name, the following message is
displayed:

This file already exists.
Do you want to overwrite it (Y or N)? N

Enter Y to overwrite the file. If you do not want to
overwrite the file, enter an N and enter new file name.

3. The cursor should now be at the BEGIN button. To begin
recording, press ENTER.

If you do not want to begin recording, use the arrow keys to
move the cursor to CANCEL and press ENTER.

4. A popup screen appears that enables you to enter a description
of the test you want to run. The information that you enter
appears at the beginning of the file when you print or display
it. This is an optional field.

Enter the test file description, if necessary. You can enter
a maximum of 70 characters.

5. Press ENTER. Recording begins and the DOS prompt is
displayed. The TestTrak program is now resident in memory and
will stay in the background capturing keystrokes and the time
between the keystrokes until you stop recording.

6. You can now start the application or enter the DOS commands
that you want to test. Remember that every key you now press
is being recorded.

Hint for Repeatability: Make sure you first enter the
disk drive and the full path for the application you want
to test.

6. Access the application that you want to test, making sure to
enter the entire path. This is an important step for the
repeatability of the test data script.



Capturing Screens and other Special Operations

Once you start recording, you can use the Record mode popup menu to
capture a full or partial screen, a palette, or perform another
operation on a particular screen. To display the menu, press CTRL-
SHIFT-T (or the current hotkey). The Record mode popup menu allows
you to

o Capture a screen
o Capture a palette
o Exit recording
o Suspend recording
o Resume recording
o Add additional time delays
o Record a warm boot
o Reset keyboard capture timer



testtrak.c
/*****************************************************************************
*
* Project: TESTTRAK
* Author : Lin Lancaster
* Version: 0.05
* Last Revised: January 2, 1991
*
* File name:
* Descriptio en inputs the
* Capture Screen eyboard buffer.
* Capture Palette es the program
* Exit Recording
* Suspend Recording
* Resume Recording
* Time Dealy
* Warm Boot
* Reset Timer
* +--------------- --------------------+
* | +------------- ------------------+ |
* | | | |
* | | | |
* | | | |
* | | Copyright (c) 1991 by TestTrak Partners. All rights reserved. | |
* | | No part of this publication may be reproduced, transmitted, | |
* | | transcribed, stored in a retrieval system, or translated into | |

BRIEF v3.0 - (c) 1984-1989 by UnderWare, Inc. Line: 1 Col: 1 4:39 am



. . . . . . . . . . . Figure 4-4 Record Mode Popup




Capture Screen

When you select Capture Screen, a popup submenu appears that allows
you to capture a full screen or a part of the screen. The captured
screen data is used for comparisons during playback mode.


Full Screen

The Full Screen option allows you to capture the entire screen
that is displayed when you select this option.

Disable Areas

The Disable Area option allows you to block out areas of the
screen that you might not be able to repeat during the next
test. For example, if you first test an application in May,
and then test it again in November, the dates will be
different and the screen won't compare. To avoid this
problem, you can block out the date area.

Once you select Disable Area, a popup message appears and you
can use the arrow keys to move around the screen. Press SHIFT
and an arrow key to block out the areas you do not want read.
To highlight only the cursor position, press the space bar.

If you want to capture most of the screen, use Disable Areas.

Enable Areas

The Enable Areas option allows you to enable parts of a
screen. This option is helpful if you want to capture only a
small part of a screen.


Capture Palette

The Capture Palette option works on VGA monitors only. It allows
you to capture a palette and puts the information into the test
data file. This function is useful for detecting differences in
the VGA palette when the test was originally recorded and the VGA's
state at playback.


Exit Recording

When you have performed all steps necessary for the test data
script on which you are working Exit Recording allows you to stop
the recording process and save the keystrokes and other operations
that were captured.

When you select Exit Recording, TestTrak automatically unloads
itself. To record another test data script, you must start
TestTrak again from the DOS prompt and select Record mode.


Suspend Recording

The Suspend Recording option allows you to enter keystrokes without
having them recorded as part of the test data script.


Resume Recording

The Resume Recording option allows you to resume recording
keystrokes as part of a test data script.


Time Delay

The Time Delay option allows you to enter a fixed period of time
between one action and another. This function is most important
when you are using a mainframe, because the amount of time between
keystrokes or other operations may vary between the time you
created the test data script and when you run it.


Warm Boot

The Warm Boot option allows you to insert a warm boot that will
occur when you play back the test data script. After inserting the
warm boot, you should stop recording since any data recorded after
this will be lost when the warm boot occurs. The warm boot will
not occur during recording.


Reset Timer

The Reset Timer option allows you to reset the keyboard capture
timer. As you are capturing keystrokes you are also capturing the
exact amount of timer between each keystroke you made. This allows
you to play back the keystrokes with the exact timing as they were
recorded originally. If, however, you took a long time between
keystrokes deciding you might not need that long between
keystrokes. If you select this option the keyboard capture timer
will be reset to zero.



Setting the Hotkey

The default key combination that brings up the hotkey is Shift>T. If you wish to use some other key combination
to bring up the popup select SET HOTKEY from the Testtrak Record
menu. You will get the message shown in Figure 4-5 below.



Record Playback Debug Modify Editors Quit

Start Recording
Set Hotkey





Current Hotkey = -T

Please type the key you want to be the new hotkey or type
the ESC key to exit without changing the hotkey.











F1 - Help TestTrak v1.00 Copyright (c) 1991 TestTrak Partners



. . . . . . . . . Figure 4-5. TestTrak Set Hotkey Menu


At this point you can either change the hotkey by pressing the key
combination you want to be the new hotkey or you can press Escape
to exit without changing the hotkey.

If you choose a hotkey combination that cannot be used you will
hear a beep and the hotkey setting will reset to the default of
T.



Chapter 5: Playing Back Test Scripts

This section describes how to playback your test data scripts. It
also describes how to create Batch Test Scripts and how to change
the playback speed.


Starting Playback Mode

To start Playback Mode from your hard disk

1. Go into the directory in which you installed TestTrak.

2. Type testtrak and press ENTER. The TestTrak Main Menu
appears, as shown in Figure 5-1.


Record Playback Debug Modify Editor Quit


















F1 - Help TestTrak v1.00 Copyright (c) 1991 TestTrak Partners




. . . . . . . . . . .Figure 5-1. TestTrak Main Menu

3. Select playback mode by using the arrow keys to move the
cursor to Playback and pressing ENTER, or typing "P". The
Playback selections menu will appear as show in Figure 5.2.
There are three major selections:

o Data File Playback
This selection is used to playback individual test
data scripts. Test data script filenames should
always end in the extension .ttd.

o Batch File Playback
This selection is used to playback a series of
individual test data scripts. The order and number
of test data scripts to be played back is stored in
the batch test file. Batch filenames will always
end in the extension .ttb.

o Set Playback Speed
When a test data script is recorded the time
between each keystroke is recorded in addition to
the keystroke. This selection allows you to modify
the time between those keystrokes when playing test
data scripts back.

o Attribute Checking
This selection is used to set attribute checking to
enabled or disabled. The default is enabled. If
attribute checking is disabled only the characters
are checked. If attribute checking is enabled both
the attributes and the characters are checked.



Record Playback Debug Modify Editors Quit

Data File Playback
Batch File Playback
Set Playback Speed
Attribute Checking












F1 - Help TestTrak v1.00 Copyright (c) 1991 TestTrak Partners



. . . . . . . . . . .Figure 5-2. Playback Main Menu


Data File Playback

Data file playback mode allows you to replay the individual test
data scripts you created in Record Mode or the TestTrak Editor to
make sure that the actions you want to take place actually take
place. When screen miscompares occur during playback, the
miscompare will be noted in the log file. This log file will have
the same name as the batch or data file being played back except it
will have an extension of .LOG.

You choose this selection by using the arrow keys to move to it and
pressing ENTER or by pressing "D". When you do either of these the
screen show in Figure 5-3 appears.


Record Playback Debug Modify Tutorial Quit

Data File Playback
Batch File Playback

Current Directory: C:\SYSCON\TESTRACK

File Name
DUMB.TTD
WP51.TTD
REBOOT.TTD
SCRCAP.TTD
SCRCAP2.TTD BEGIN CANCEL




First enter the file name. Then select
either begin or cancel. You can exit at
any point by pressing Esc.

F1 - Help F2 - Change Directory F3 - Swap Boxes Esc - Exit


F1 - Help TestTrak v1.00 Copyright (c) 1991 TestTrak Partners




. . . . . . . . .Figure 5-3. Data File Playback Screen


The list of test data scripts in the current directory will be
displayed in the pick box to the left. If you wish to choose a test
data script from a different directory press F2 and then enter the
directory you want.


To begin playing back the test data script:

1. Select the test data script you want by one of two methods -

a. Press F3 to move the cursor to the file name box.
Enter the filename (including path if necessary)
and press ENTER. The cursor will move to the BEGIN
button.

b. Press F3 key to move the cursor into the pick box
and select a file to playback, or enter the name of
the file and press ENTER. The cursor will move to
the BEGIN button.

2. Press ENTER to begin playing back the file. If you have made
a mistake in your file selection you can cancel by using the
arrow keys to move the cursor to the CANCEL button and then
pressing ENTER.

3. TestTrak will now go resident and begin playing the test data
script back at whatever speed multiplier you had previously
selected in the Set Playback Speed Selection. When the test
data script is finished playing back TestTrak will unload
itself from memory.

4. You can now check the results of the test data script playback
by checking the log file. This file will be in the same
directory as the test data script, have the same name as the
test data script played back but have an extension of .log. A
sample log file output is shown in Figure 5-4.



Comparison of screen #1 - Failed
Comparison of screen #2 - Passed
Comparison of screen #3 - Failed


. . . .Figure 5-4. Sample Log File Output - Data Script Playback



Batch File Playback

A batch file is an ASCII file whose lines are the path and file
name of the data files that you want to run. The data files are
played back in the order in which they appear in the batch file.
The extension .ttb is attached to the batch file automatically.
There is no limit to the amount of data files in a batch, and there
is no limit to the amount of batch files.

You cannot have a batch within a batch, but you can have batches
and data files for several different tests. You can also mix and
match files from several different batches.

The Batch File Playback option allows you to playback a batch file
of test data scripts. A batch file is an ASCII file that lists the
names of a number of data files. You select the following Batch
File Playback by using the arrow keys to move to this selection and
press ENTER or by pressing "B". When you select this option, the
following screen is displayed.


Record Playback Debug Modify Tutorial Quit

Data File Playback
Batch File Playback

Current Directory: J:\SYSCON\TESTRACK

File Name
DOTWICE.TTB
DELAY.TTB
TEMP.TTB
SIZE.TTB
TWO.TTB BEGIN CANCEL




First enter the file name. Then select
either begin or cancel. You can exit at
any point by pressing Esc.

F1 - Help F2 - Change Directory F3 - Swap Boxes Esc - Exit


F1 - Help TestTrak v1.00 Copyright (c) 1991 TestTrak Partners




. . . . . . . . .Figure 5-5. Batch File Playback Screen



The list of batch files in the current directory will be displayed
in the pick box to the left. If you wish to choose a batch file
from a different directory press F2 and then enter the directory
you want.

To begin playing back the batch file:

1. Select the batch file you want by one of two methods -

a. Press F3 to move the cursor to the file name box.
Enter the filename (including path if necessary)
and press ENTER. The cursor will move to the BEGIN
button.

b. Press F3 to move the cursor into the pick box and
select a file to playback, or enter the name of the
file and press ENTER. The cursor will move to the
BEGIN button.

2. Press ENTER to begin playing back the file. If you have made
a mistake in your file election you can cancel by using the
arrow keys to move the cursor to the CANCEL button and then
pressing ENTER.

3. TestTrak will now go resident and begin playing the first test
data script in the batch file back at whatever speed
multiplier you had previously selected in the Set Playback
Speed Selection. When the first test data script is completed,
it will begin playing back the next test data script in the
batch file. It will continue this way until it has played back
all the test data scripts in the batch file. When all the test
data script are finished playing back, TestTrak will unload
itself from memory.

4. You can now check the results of the batch playback by
checking the log file. This file will be in the same directory
as the batch file, have the same name as the batch file played
back but have an extension of .log. A sample log file output
is shown in Figure 5-6.


Starting playback of j:\syscon\testtrak\wp51.ttd.
Comparison of screen #1 - Passed
Comparison of screen #2 - Passed
Comparison of screen #3 - Passed

Starting playback of j:\syscon\testtrak\norton.ttd.
Comparison of screen #1 - Failed
Comparison of screen #2 - Passed
Comparison of screen #3 - Failed

Testing completed: TWOFILE.TTB.




. . . . . Figure 5-6. Sample Log File Output - Batch Playback




Set Playback Speed

The Set Playback Speed option enables you to select one of six
speeds at which to playback your file. These speeds include

Maximum, which enables you to playback your file at the
maximum speed possible.

Four Times Speed, which enables you to playback your file at
four times the speed at which it was created.

Two Times Speed, which enables you to playback your file at
two times the speed at which it was created.

Same Speed, which enables you to playback your file at the
same speed at which it was created.

Half Speed, which enables you to playback your file at half
the speed at which it was created.

Slow Speed, which enables you to playback your file at the
slowest possible speed.


Select Set Playback Speed from the main Playback menu by using the
arrow keys to move the Set Playback Speed selection and pressing
ENTER or by pressing "S". When you select this choice the following
screen in Figure 5-9 appears.


Record Playback Debug Modify Editor Quit

Data File Playback
Batch File Playback
Set Playback Speed

Maximum Speed
Four Times Speed
Two Times Speed
Same Speed
Half Speed
Slow Speed











F1 - Help TestTrak v1.00 Copyright (c) 1991 TestTrak Partners



. . . . . . . . .Figure 5-9. Set Playback Speed Screen


Select the speed option you want by using the arrow keys to move to
that location and pressing ENTER or by pressing the highlighted
letter of the selection you want.





Set Attribute Checking

The Set Attribute Checking option allows you to determine whether
only characters or both characters and attributes should be
checked. This option is useful if you've developed your tests on a
VGA system and are now running the tests on an MDA. The characters
will remain the same on the screen but the attributes are likely to
be different because VGA is color and MDA is monochrome. The
default for this selection is attribute checking enabled. This
selection is not saved so if you want to disable attribute checking
you must select that each time you start up TestTrak.

Select Attribute Checking from the main Playback menu by using the
arrow keys to move the Attribute Checking selection and pressing
ENTER or by pressing "A". When you select this choice the following
screen appears:



Record Playback Debug Modify Editors Quit

Data File Playback
Batch File Playback
Set Playback Speed
Attribute Checking

Disable
Enable













F1 - Help TestTrak v1.00 Copyright (c) 1991 TestTrak Partners


. . . . . . . .Figure 5-10. Set Attribute Checking Screen


Select the attribute checking option you want by using the arrow
keys to move to that location and pressing ENTER or by pressing the
highlighted letter of the selection you want.

Chapter 6: Debugging Test Data Scripts

Debug mode allows you to display screen miscompares with the
application that you are testing. There are two types of Debug
that you can perform.

o Run Until Error
o Single-Step Debug


Run Until Error
The Run Until Error option allows the program to play back either
a batch file or a data file until TestTrak detects a screen that
does not compare. When the screen is detected, the areas that do
not compare are highlighted and blinking.

Single-Step Debug
The Single-Step Debug option allows you to step through the test
data script keystroke by keystroke (or operation by operation). As
with Run Until Error, when a screen is detected that does not
compare, the program stops, and the areas that do not compare are
highlighted and blinking.



Starting Debug Mode

To start Debug Mode from your hard disk

1. Go into the directory in which you installed TestTrak.

2. Type testtrak and press ENTER. The TestTrak Main Menu
appears, as shown in Figure 6-1.



Record Playback Debug Modify Editor Quit
















F1 - Help TestTrak v1.00 Copyright (c) 1991 TestTrak Partners


. . . . . . . . . . .Figure 6-1. TestTrak Main Menu


3. Select debug mode by using the arrow keys to move the cursor
to Debug and pressing ENTER, or typing "D". The Debug
selections menu will appear as show in Figure 6.2. There two
major selections, as stated before are:

o Run Until Error Debug
o Single-Step Debug


Record Playback Debug Modify Editor Quit

Run Until Error
Single Step Debug














F1 - Help TestTrak v1.00 Copyright (c) 1991 TestTrak Partners




. . . . . . . . . . . Figure 6-2. Debug Main Menu





Run Until Error Debug

You choose this selection by using the arrow keys to move to it and
pressing ENTER or by pressing "R". When you do either of these the
screen show in Figure 6-3 appears.



Record Playback Debug Modify Editor Quit

Run Until Error
Single Step Debug

Current Directory: J:\SYSCON\TESTTRAK

File Name
DUMB.TTD
WP51.TTD
REBOOT.TTD
SCRCAP.TTD
SIZE.TTD BEGIN CANCEL
SCRCAP2.TTD
EDITOR.TTD
TEST1.TTD
SPECIAL.TTD
KEYCHK.TTD First enter the file name. Then select
either begin or cancel. You can exit at
any point by pressing Esc.

F1 - Help F2 - Change Directory F3 - Swap Boxes Esc - Exit


F1 - Help TestTrak v1.00 Copyright (c) 1991 TestTrak Partners



. . . . . . . . . Figure 6-3. Debug File Entry Screen


The list of test data scripts in the current directory will be
displayed in the pick box to the left. If you wish to choose a test
data script from a different directory press F2 and then enter the
directory you want.

To begin debugging a test data script:

1. Select the test data script you want by one of two methods -

a. Press F3 to move the cursor to the file name box.
Enter the filename (including path if necessary)
and press ENTER. The cursor will move to the BEGIN
button.

b. Press F3 to move the cursor into the pick box and
select a file to play back, or enter the name of
the file and press ENTER. The cursor will move to
the BEGIN button.

2. Press ENTER to begin debugging the file. If you have made a
mistake in your file selection you can cancel by using the
arrow keys to move the cursor to the CANCEL button and then
pressing ENTER.

3. TestTrak will now go resident and begin playing the test data
script back at whatever speed multiplier you had previously
selected in the Set Playback Speed Selection. When any screen
miscompares occur the areas on the screen will be displayed as
blinking highlighted areas. When you are finished looking at
the screen miscompare press the Space bar to continue. When
the test data script is finished playing back for debugging
TestTrak will unload itself from memory.



Single Step Debug

You choose this selection by using the arrow keys to move to it and
pressing ENTER or by pressing "S". When you do either of these the
screen show in Figure 6-3 appears.



Record Playback Debug Modify Editor Quit

Run Until Error
Single Step Debug

Current Directory: J:\SYSCON\TESTTRAK

File Name
DUMB.TTD
WP51.TTD
REBOOT.TTD
SCRCAP.TTD
SIZE.TTD BEGIN CANCEL
SCRCAP2.TTD
EDITOR.TTD
TEST1.TTD
SPECIAL.TTD
KEYCHK.TTD First enter the file name. Then select
either begin or cancel. You can exit at
any point by pressing Esc.

F1 - Help F2 - Change Directory F3 - Swap Boxes Esc - Exit


F1 - Help TestTrak v1.00 Copyright (c) 1991 TestTrak Partners



. . . . . . . . . Figure 6-4. Debug File Entry Screen


The list of test data scripts in the current directory will be
displayed in the pick box to the left. If you wish to choose a test
data script from a different directory press F2 and then enter the
directory you want.

To begin debugging a test data script:

1. Select the test data script you want by one of two methods -

a. Press F3 to move the cursor to the file name box.
Enter the filename (including path if necessary)
and press ENTER. The cursor will move to the BEGIN
button.

b. Press F3 to move the cursor into the pick box and
select a file to play back, or enter the name of
the file and press ENTER. The cursor will move to
the BEGIN button.

2. Press ENTER to begin debugging the file. If you have made a
mistake in your file selection you can cancel by using the
arrow keys to move the cursor to the CANCEL button and then
pressing ENTER.

3. TestTrak will now go resident and begin playing the test data
script back at whatever speed multiplier you had previously
selected in the Set Playback Speed Selection.

4. Before any key will be acted on it will be displayed for you
in a pop-up box like that shown in Figure 6-5. When any screen
miscompares occur the areas on the screen will be displayed as
blinking highlighted areas. When you are finished looking at
the screen miscompare press the Space bar to continue. When
the test data script is finished playing back for debugging
TestTrak will unload itself from memory.



06-16-91 09:08p Directory I:\WP51\TESTTRAK\*.*
Document size: 0 Free: 14,180,352 Used: 385,484 Files: 15

. Current .. Parent
35LABEL .LBL 12,134 05-26-91 01:52p 514LABEL.LBL 15,359 05-26-91 01:53p
CHAPTER1. 20,735 06-16-91 07:22p CHAPTER2. 21,170 06-16-91 07:24p
CHAPTER3. 28,645 06-16-91 01:27p DEBUG . 26,232 06-16-91 01:28p
EDITOR . 35,820,368 06-16-91 01:27p
LIN .DOC 17,110,414 05-26-91 06:36p
MODIFY . 25,761,286 06-16-91 09:01p
RECORD . 38,1 The key = F7 25,358 06-16-91 01:29p
USING . 26,7 Hit any key to continue











1 Retrieve; 2 Delete; 3 Move/Rename; 4 Print; 5 Short/Long Display;
6 Look; 7 Other Directory; 8 Copy; 9 Find; N Name Search: 6




. . . . . . . . . .Figure 6-5. Next Keystroke Pop-Up



Chapter 7: Using the TestTrak Batch File Editor


This chapter describes the TestTrak Batch File Editor.



Batch File Editor

This selection is used to create and modify batch test files. Each
batch test file is simply an ASCII text file containing the path
and name of each of the test data script files you want to run. You
may use this editor or any ASCII text editor to create batch test
files.



Edit Batch File

The Edit Batch File option enables you to add or remove a file(s)
from a batch file. A data file can be in several different batch
files at the same time. You may also use any text editor to create
batch files because batch files are simply ASCII text files
containing the name and path of test data script file names. Choose
this selection from the Editors menu by using the arrow keys to
move to this selection and pressing ENTER or by pressing "B". When
you do the following screen will appear:



Record Playback Debug Modify Editors Quit

Data File Editor
Batch File Editor

Current Directory: J:\CODERUN\TESTTRAK

File Name
TWO.TTB TWO.TTB
NEW.TTB
TENLINE.TTB
SS.TTB
TWOTWO.TTB BEGIN CANCEL
DUMB.TTB



First enter the file name. Then select
either begin or cancel. You can exit at
any point by pressing Esc.

F1 - Help F2 - Change Directory F3 - Swap Boxes Esc - Exit



F1 - Help TestTrak v1.00 Copyright (c) 1991 TestTrak Partners



. . . . . . . . Figure 7-1. Edit Batch File Entry Screen


Select the batch file you want to edit by entering the filename
(including path if necessary) and press ENTER. The following
editing screen will appear.



Record Playback Debug Modify Editors Quit

Data File Editor
Batch File Editor

Current Directory: J:\CODERUN\TESTTRAK
Pick Box Chosen Files

DUMB.TTD norton.ttd
NORTON.TTD wp51.ttd
WP51.TTD J:\CODERUN\TESTTRAK\NORTON.TTD






F2 - Change Dir F10 - Save File Ins - Ins Line Del - Del Line


F1 - Help TestTrak v1.00 Copyright (c) 1991 TestTrak Partners



. . . . . . . . . . Figure 7-2. Batch Editor Screen



The box to the left will hold the name of valid data script files
in the current directory. To move one of the data files into the
batch file press ENTER.

To move between the two boxes use the left/right arrow keys.

To change the current directory use the F2 key.

To move a file from the pick box at the left into the batch file
box use the arrow keys to position the cursor over the file in the
pick box you want and then press the ENTER key.

When you are finished editing press F10 to save the file and exit.
If you do not wish to save the changes to the file just press ESC.








Chapter 8: Using the TestTrak Data File Editor

This chapter describes the TestTrak Data File Editor.


Introduction To the Data File Editor

The TestTrak Editor portion of TestTrak for Text allows you to edit
existing data files that were created with TestTrak or to create
new files by typing ASCII text. This function is especially useful
for creating a test file for an application that is not quite ready
for testing, but for which you already have a functional
specification. Since the functional specification gives you an
idea of the application's screen layouts and functionality, you can
decide the types of tests you want to run, and you can begin
entering the keystrokes and other actions that you want included in
the test. Then, when you receive the final application software,
you can play back the keys and operations that you created through
Modify. The TestTrak Editor is also useful for viewing test data
scripts.

Any text you enter into a file that you create in TestTrak Editor
is put into the same file structure as the data files that are
created in Record mode. Therefore, when using the TestTrak Editor,
it is important that you keep in mind the same test script design
issues discussed in Chapter 2 of this manual. In other words,

o Keep the test data scripts as small as possible.

o Make sure that the test conditions are repeatable.

o Make sure that each test data script starts from a known place
and ends in a known place.

o Try to design scripts that find errors.

o Keep the concept of "boundary" testing in mind. In other
words, the boundaries of each test script should be at a place
in the application where you would expect to find an error.

By designing test data scripts that follow these guidelines, you
should be able to keep further editing and retesting to a minimum.



In addition, remember that while the TestTrak Editor is similar to
the Modify function, it runs independently of the application you
are testing. This means that you cannot capture screens, palettes,
or time delay information.



Getting Around in the Data File Editor

The TestTrak Editor uses cursor keys to move throughout the menu
selections. The following is a brief summary of various special
keys which will make using the TestTrak Editor program easier. Like
all programs experiment and usage will be the greatest teacher.

All Menu Selection (General):

Cursor Right: Moves selection bar one position to the
right. If selection bar is in last
position, the bar is moved to the first
menu selection item.

Cursor Left: Moves selection bar one position to the
left. If the selection bar is on first
selection, the bar is moved to the last
menu selection item.

Cursor Up: Moves to the previous menu line except in
the Data Escape selection.

Cursor Down: Enters into the selected menu item.

Tab, Space Bar: See Cursor Right

Shift Tab: See Cursor Left

Enter: See Cursor Down

Esc: See Cursor Up: Or a Special key in Data
Escape selection.

First Letter: First Highlighted letter in menu
selections causes selection of selected
item.

F1: Anytime F1 is depressed, the Help menu is
invoked for menu line.


Data Escape Menus:

Cursor Right: In Dual Mode, Moves cursor to the column
to the right. If cursor at second column,
moves cursor to right column. In Single
Mode, cursor does not move.

Cursor Left: In Dual Mode, Moves cursor to the left
column. If cursor is in Left column, the
cursor moves to right column. In Single
mode, cursor does not move.

Cursor Up: Moves the cursor up one line.

Cursor Down: Moves the cursor down one line.

Page Up: Moves cursor up ten lines.

Page Down: Moves cursor down ten lines.

Home: Moves cursor to first line.

End: Move cursor to the last legal character
in the work area.

Insert: Inserts one space at the current cursor
location.

Delete: Deletes one character at the cursor
location.



Starting the TestTrak Data File Editor

To start the TestTrak Data File Editor from your hard disk

1. Go into the directory in which you installed TestTrak.

2. Type testtrak and press ENTER. The TestTrak Main Menu
appears, as shown in Figure 8-1.



Record Playback Debug Modify Editor Quit























F1 - Help TestTrak v0.04 Copyright (c) 1991 TestTrak Partners




. . . . . . . . . . .Figure 8-1. TestTrak Main Menu


3. Select the data file editor from the Editors menu by using the
arrow keys to move the cursor and pressing ENTER, or typing
"D". When you do the main TestTrak Data File Editor screen
shown in Figure 8-2 will appear.






[sample screen]
Data File Special Help Exit




. . . . . . . . .Figure 8-2. TestTrak Editor Main Menu


The following sections discuss each of these menu options and any
submenus they may have.



Data

The Data option allows you to enter a test data script. It also
provides you with the same functions that are available in Record
mode, allows you to decide which keystrokes you want to capture,
how you want your file displayed as you work with it, and other
functions.

When you select the Data option from the Main Menu, the following
screen is displayed.



Data File Special Help Exit

Escape All-Keys Special Reset Fn11 Fn12 Setup Help

Status & Modes: Single Entry


1:c
2:d
3:
4:\
5:w
6:p
7:5
8:1
9:^M
10:

cd \wp51^M
Open File: None









. . . . . . . . . . . .Figure 8-3. The Data Menu


Each of these menu options is discussed below.




Escape

When you are in the data entry screen and you press key, the
following menu bar will appear (special selection mode). The Escape
selection on the menu bar will be blinking to indicate you can now
select All-Keys, Special, Fn11, and Fn12 menu selection items
without altering the screen. The blinking Escape selection mean you
are now in a special selection mode. When used in conjunction with
All-Keys, Special, Fn11, and Fn12, this special selection mode
allows the user to enter special functions into the data work area.
Remember during the Blinking Escape mode, if you press the arrow
keys, the viewed data area will be removed from the screen, the
data however, will not be lost.
Example: The following is an example of adding the Palette Capture
function into the test file:

Start Testtrak
At the main Testtrak screen:
Select Editor
Select Data Editor
At the Data Editor Screen:
Select Data Selection
Select Escape Selection
Press the following keys:


* Notice Escape Selection item is blinking

* Notice the P is blinking in the Special
selection and a sub-menu pops up.

* Notice in work area a Pal appears. This
indicates a palette capture has been entered
into the work area.
* The special sub-menu goes away.
* You are back to the work area. You now can
begin typing any key.

* The data work area should now look as follows:

1. a
2. b
3. Pal
4.
5.
6.
7.
8.
9.
10.

Please review the special functions below.


[sample screen]
Escape All-Keys Special Reset Fn11 Fn12 Setup
Help




. . . . . . . . . . . .Figure 8-4. Escape Screen


This screen allows you to enter a new test data script or display
an existing one. Each keystroke or operation is displayed on one
line in the text box. You can enter any number of keystrokes or
operations, but the buffer is limited to 2K.

The blank bar in the bottom, left-hand corner shows keys that are
pressed in combination with other keys, or status modes such as
Insert. For example, if one operation is ALT-T, the T would appear
in the text box, and the ALT would appear in the bar as either an
upper- or a lower-case A. (If you press a key such as ALT or CTRL
on the left-hand side of the space bar, it is displayed as an
upper-case letter; if you press the same key on the right-hand side
of the space bar, it is displayed as a lower-case letter.)


All-Keys

The All-Keys option allows you to toggle between capturing all the
keystrokes that you make when creating a data file and capturing
only some of your keystrokes. The keystrokes that are not normally
captured (PgUp, PgDn, Home, End, Arrow keys) are used to move
around in the test data script you are creating. If you need to
capture one of these keys ( for example, a Home key), you need to
change into All-Keys mode. When All-Keys mode is on and you press
the Home key, the Home key will be put into the test data script as
a character. If All-Key mode was off, pressing the Home arrow key
would cause you to move to the position of the top character in the
test data script you were editing.



Special

The Special option provides all functions that are available to you
in Record mode, plus a GO TO option that allows you to go to a
particular line number in the data file. This function is only
active when you are entering data and press the key once,
followed by a

key. Once the

is blinking on the Special menu
selection, you may add anyone of the following functions to the
Data work area.

These functions include

o Capture a screen
o Capture a palette
o Capture the time delay between keystrokes
o Record a warm boot
o GoTo character number
o Escape Key input


Capture Screen

This selection allows you to indicate that you want to capture
a screen when the test data script reaches this point.


Capture Palette

The Capture Palette option works on VGA monitors only. It
allows you to capture a palette with or without the screen and
puts the information into the test data file. This function
is useful for detecting differences in the test palette and
the VGA's palette.


Time Delay

The Time Delay option allows you to enter a fixed period of
time between one action and another. This function is most
important when you are using a mainframe, because the amount
of time between keystrokes or other operations may vary
between the time you created the test data script and when you
run it.


Warm Boot

The Warm Boot option allows you to insert a warm boot that
will occur when you play back the test data script. After
inserting the warm boot, you should stop recording since any
data recorded after this will be lost when the warm boot
occurs. The warm boot will not occur during recording.



GoTo Character Number

This selection allows you to go directly to a particular
character number in the test data script.

Escape Key Input

This selection allows you to insert an escape key as a
character in the test data script. You must input the Escape
key here because the Escape key is normally used to get to
this menu bar.



Reset

Reset clears out the current work area. You would use this option
when you are through with one file (and have closed it) and want to
move on to another file.




Fn11

The F11 option allows you to insert an F11 keystroke into the data
file. To use this option while entering data, press ESC at the
line where you want to put an F11. When the flashing ESC appears
on the data menu, press the "F" key by itself to input an F11 into
the test script. If you want some combination of Alt, control
and/or shift F11; press the "F" key in combination with the Alt,
control and/or shift key you want.


To return to the file, press E. The data file is displayed again
with the cursor on the last line you entered.


Fn12

The F12 option allows you to insert an F12 keystroke into the data
file. To use this option while entering data, press ESC at the
line where you want to put an F12. When the flashing ESC appears
on the data menu, press the "N" key by itself to input an F12 into
the test script. If you want some combination of Alt, control
and/or shift F12; press the "N" key in combination with the Alt,
control and/or shift key you want.

To return to the file, press E. The data file is displayed again
with the cursor on the last line you entered.


Setup

The Setup option allows you to display your data file in three
different ways.

Single

The Single option displays the file in one column, with each
keystroke being displayed on each numbered line.


Dual

The Dual option displays two columns of keystrokes. The
columns are continuous, so that when you scroll through a
column, the lines in both columns move.


View

The View option allows you to display entire lines of text.
Data cannot be entered or changed in this mode, only viewed.




File

The File option allows you to manage your files, including opening
a new file, merging two files, listing, deleting, and closing
files, and changing directories. When you select File, the
following menu is displayed.



[sample screen]
Open List Delete Merge Close Header Directory Help




. . . . . . . . . . . . .Figure 8-5. File Menu




Open

The Open option allows you to open a new or existing file. To edit
an existing file, enter the name of the file (the extension
defaults to .ttd) and press RETURN. The new file is displayed.


List

The List option allows you to list one file or all data files in
the current directory. To display all files, type an asterisk (*)
and press RETURN.


Delete

The Delete option allows you to delete a file. Enter the name of
the file you want to delete and press RETURN.


Merge

The Merge option allows you to merge a file that is already opened
with the contents of another file. To merge two files, you must be
in one file. Then, select Merge and enter the name of the file you
want to merge and press RETURN. The merged or new test data file
is always added to the end of the currently opened file.

This option allows you to save time because you can create a file
of a particular operation or series of keystrokes that you expect
to use frequently. Then, instead of having to type the operation
or keystrokes into a test data file each time you want to use them,
you can use Merge to copy the contents of the file into your test
file.


Close

The Close option allows you to close the file you are working on.
If you try to exit the TestTrak Editor without closing the file, a
message is displayed telling you that the file is still open and
asking you if you want to close it.


Header

The Header option allows you to add a description of the file that
you created. This description appears at the beginning of the file
when you display or print the file. The header can be up to 70
characters.


Directory

The Directory option displays the name of the current directory and
allows you to change to another directory. This directory defaults
to the directory that TestTrak is located in.


Special

The Special option allows you to select certain conditions for the
test. These conditions are all toggles that you can select or
deselect.


Color

The Color option allows you to select color mode or mono mode.


Auto

The Auto mode allows you to turn the auto-save feature on or off.
If you turn it on, your file is saved automatically every five
minutes, if a file is open.


Print

The Print option allows you to print out all keystrokes in the
file, including any key combinations. The printout shows the line
number as well as the character or operation on that line.


Key Code: d Ins
Key Code: i Ins
Key Code: r Ins
Key Code: / Ins
Key Code: w Ins
Key Code: ^M Ins
Capture:
Key Code: t Ins
Key Code: m Ins
Key Code: ^M Ins
File End:

. . . . . .Figure 8-6. Sample Printout Using the Print Option



Using the TestTrak Editor

This section provides basic instructions for creating a test data
file. Once you know how to create a file, you will be able to edit
a file as well.

1. Select File from the TestTrak Editor Main Menu.

2. Enter the name of a new or existing file. If you are opening
a new file, you can also enter a description of the file, as
you can in Record mode.

3. Press ESC to go back to the Main Menu.

4. Select Data. The following menu is displayed.

5. Select Escape. The following screen is displayed.




Data File Special Help Exit

Escape All-Keys Special Reset Fn11 Fn12 Setup Help

Status & Modes: Single Entry


1:c
2:d
3:
4:\
5:w
6:p
7:5
8:1
9:^M
10:

cd \wp51^M
Open File: None







. . . . . . . . . . Figure 8-7. Sample File Display


6. When you are through entering your test data script, press ESC
twice and then F to get back to the File menu.

7. Select Close to close the file.