Row Access Order
300
Chapter 11 - Working with Datapools
Datapool Cursor
The datapool
cursor
, or row-pointer, can be shared among all virtual testers who
access the datapool, or it can be unique for each virtual tester.
Sharing a datapool cursor among all virtual testers allows for a coordinated test.
Because each row in the datapool is unique, each virtual tester can share the same
cursor and still send unique records to the database.
In addition, a shared cursor can be persistent across suite runs. For example, suppose
that the last datapool row accessed in a suite run is row 100:
s
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.
s
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.
Note:
Virtual testers running SQABasic test scripts can share a cursor when playback
occurs in a TestManager suite, but not when playback occurs in Robot.
For information about defining the scope of a cursor, see the description of the
Cursor
argument in the
Rational Robot User's Guide
.
Row Access Order
Row access order is the sequence in which datapool rows are accessed at test runtime.
With GUI test scripts, you control the row access order of the datapool cursor through
the
sequence
argument of the SQABasic
SQADatapoolOpen
command.
With VU test scripts, you control row access order through the
Access Order
setting in
the Robot Configure Datapool in Script dialog box. (See the
Rational Robot User's Guide
.)
For other types of test scripts, see the Rational Test Script Services manual for your
language.
Datapool Limits
A datapool can have up to 150 columns if Robot or TestManger automatically
generates the data for the datapool, or 32,768 columns if you import the datapool from
a database or other source. Also, a datapool can have up to 2,147,483,647 rows.
