Files Generated

 Files Generated During Recording

Assume that the recorded test has been given the name ‘vuser’ and is stored under c:\tmp. Following is a list of the more important files that are generated after recording:

vuser.usr - Contains information about the virtual user: type, AUT, action files, and so forth.

vuser.bak - A copy of Vuser.usr before the last save operation.

default.cfg - Contains a listing of all run-time settings as defined in the VuGen application (think time, iterations, log,

web).

vuser.asc - The original recorded API calls.

vuser.grd - Contains the column headers for grids in database scripts.

default.usp - Contains the script’s run logic, including how the actions sections run.

init.c - Exact copy of the Vuser_init function as seen in the VuGen main window.

run.c - Exact copy of the Action function as seen in the VuGen main window.

end.c - Exact copy of the Vuser_end function as seen in the VuGen main window.

vdf.h - A header file of C variable definitions used in the script.

\Data -  The Data directory stores all of the recorded data used primarily as a backup. Once the data is in this

directory, it is not touched or used. For example,Vuser.c is a copy of run.c.

Files Generated During Replay

This section describes what occurs when the Vuser is replayed.

1 The options.txt file is created which includes command line parameters to the preprocessor.

2 The file Vuser.c is created which contains ‘includes’ to all the relevant .c and .h files.

3 The c preprocessor cpp.exe is invoked in order to ‘fill in’ any macro definitions, precompiler directives, and so on, from the development files.

The following command line is used:

cpp -foptions.txt

4 The file pre_cci.c is created which is also a C file (pre_cci.c is defined in the options.txt file). The file logfile.log (also defined in options.txt) is created containing any output of this process. This file should be empty if there are

no problems with the preprocessing stage. If the file is not empty then its almost certain that the next stage of compilation will fail due to a fatal error.

5 The cci.exe C compiler is now invoked to create a platform-dependent pseudo-binary file (.ci) to be used by the virtual user driver program that will interpret it at run-time. The cci takes the pre_cci.c file as input.

6 The file pre_cci.ci is created as follows:

cci -errout c:\tmp\Vuser\logfile.log -c pre_cci.c

7 The file logfile.log is the log file containing output of the compilation.

8 The file pre_cci.ci is now renamed to Vuser.ci. Since the compilation can contain both warnings and errors, and since the driver does not know the results of this process, the driver first checks if there are entries in the logfile.log file. If there are, it then checks if the file Vuser.ci has been built. If the file size is not zero, it means that the cci has

succeeded to compile - if not then compilation has failed and an error message will be given.

9 The relevant driver is now run taking both the .usr file and the Vuser.ci file as input. For example: mdrv.exe -usr c:\tmp\Vuser\Vuser.usr -out c:\tmp\Vuser –file c:\tmp\Vuser\Vuser.ci

The .usr file is needed since it tells the driver program which database is being used. From here it can then know which libraries need to be loaded for the run.

10 The output.txt file is created (in the path defined by the ‘out’ variable) containing all the output messages of the run. This is the same output as seen in both the VuGen runtime output window and the VuGen main lower window.

The vugen.dat file resides in the M_LROOT\dat directory and contains general information about VuGen, to be used by both the VuGen and the Controller.

The mdrv.dat file contains a separate section for each protocol defining the location of the library files and driver executables.