DoxRunner
​
Overview
Test data is critical to the operation of a script in a scenario.
DoxRunner's Test Case and Script operations support three methods for handling test data:
​
There is only limited support for VTS. That is, there is a section reserved for VTS in the documents, but DoxRunner's Script operations only recognizes a subset of its functions.
​
Test accounts can be included and managed in either a Text Data File or a LoadTest Database table.
Text data files
​
A Text Data File parameter is LoadRunner's native method of handling data.
DoxRunner supports Text Data Files by:
-
providing a framework for documenting them as rules (in a Test Case and/or in a Solution document);
-
providing a process whereby those rules can be automatically applied to a raw script using DoxRunner's Test Case and Script operations.
​
LoadTest Database parameters
The LoadTest database option for managing data uses a MySQL database, which is superior to Text Data Files and VTS.
Although native LoadRunner doesn't support this method, DoxRunner's Script operations provides a mechanism whereby it can, using an easy point-and-click parameterization of database table columns, plus the creation of skeleton functions to tailor database interaction.
Virtual Table Server (VTS) parameters
The Virtual Table Server (VTS) is a newer way of managing data available from LoadRunner v12.0. It allows data to be shared between scripts in a test.
DoxRunner's Test Case and Script operations provide limited support for this method.
In any case the LoadTest Database functionality is superior.
​
​
Test accounts
​
Test accounts should be documented as either a Text Data File or as a table in the LoadTest Database.