top of page
TopOfPage

 

Test Data Operations

 

Overview

 

Test data is critical to the operation of a script in a scenario.

 

DoxRunner supports three methods for handling test data:

​

DoxRunner support for VTS is limited.

​

Test accounts can be included and managed in either a text data file or a LoadTest Database table.

 

TextDataFileOperations
LoadTestDatabaseOperations
VTSOperations

 

Text data files

​

This is the native LoadRunner way of applying data during a test.

​

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 the Process Raw operation.

​

​

LoadTest database

​

This is an alternative way of applying data during a test. By the use of a MySQL database much better control of data, especially complex data, can be achieved both during a test and between tests. 

​

It is not directly supported by LoadRunner but it can be manually instrumented.

​

It is fully supported by the Process Raw operation, which provides easy point-and-click parameterization of database table columns, plus the creation of skeleton functions to tailor database interaction.

​

VTS

​

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.

​

It is not supported by the Process Raw operation, however there is no reason why it cannot be manually implemented into a script once the Process Raw operation has processed a raw script.

​

Test Accounts

​

Test accounts should be documented as either a text data file or as a table in the LoadTest database.

 

TestAccounts
bottom of page