Managing Datapool Files
What Is a Datapool?
10-3
Rational TestManager User's Guide Managing Datapool Files
A datapool consists of two files:
¾
Datapool values are stored in a text file with a .csv extension.
¾
Datapool column names are stored in a specification(.spc) file. The Robot or
TestManager software is always responsible for creating and maintaining this
file. You should never edit this file directly.
.csv and .spc files are stored in the Datapool directory of your Robot project.
Unless you import a datapool, the Robot or TestManager software automatically
creates and manages the .csv and .spc files based on instructions you provide through
the user interface.
If you import a datapool, you are responsible for creating the .csv file and populating
it with data. However, the Rational Test software is still responsible for creating and
managing the .spc file for the imported datapool.
For information about importing datapools, see Rational TestManager User's Guide.
Datapool Cursor
The datapool cursor, or row-pointer, can be shared among all users who access the
datapool, or it can be unique for each user.
Sharing a datapool cursor among all users allows for a coordinated test. Because each
row in the datapool is unique, each user can share the same cursor and still send
unique records to the database.
Also, a shared cursor can be persistent across suite runs. For example, suppose the
last datapool row accessed in a suite run is row 100:
¾
If the cursor is persistent across suite runs, datapool row access resumes with
row 101 the first time the datapool is accessed in a new suite run.
¾
If the cursor is not persistent, datapool row access resumes with row 1 the first
time the datapool is accessed in a new suite run.
For information about defining the scope of a cursor, see the description of the
NOTE: TestManager automatically copies a .csv file to each Agent computer that
uses it. If an Agent's .csv file becomes out-of-date, TestManager automatically
updates it.
NOTE: GUI users can share a cursor when playback occurs in a TestManager
suite, but not when playback occurs in Robot.
