Default.usd:Contains the script's run logic,including how the actions sections run.
[RunLogicRunRoot:flights]
MercIniTreeSectionName="flights"
RunLogicObjectKind="Action"
Name="flights"
RunLogicActionType="VuserRun"
MercIniTreeFather="RunLogicRunRoot"
[RunLogicEndRoot:vuser_end]
MercIniTreeSectionName="vuser_end"
RunLogicObjectKind="Action"
Name="vuser_end"
MercIniTreeFather="RunLogicEndRoot"
RunLogicActionType="VuserEnd"
[RunLogicInitRoot:vuser_init]
MercIniTreeSectionName="vuser_init"
RunLogicObjectKind="Action"
Name="vuser_init"
MercIniTreeFather="RunLogicInitRoot"
RunLogicActionType="VuserInit"
[RunLogicRunRoot:Login_System]
MercIniTreeSectionName="Login_System"
RunLogicObjectKind="Action"
Name="Login_System"
RunLogicActionType="VuserRun"
MercIniTreeFather="RunLogicRunRoot"
[RunLogicRunRoot:Action]
MercIniTreeSectionName="Action"
RunLogicObjectKind="Action"
Name="Action"
MercIniTreeFather="RunLogicRunRoot"
RunLogicActionType="VuserRun"
[Profile Actions]
Profile Actions name=vuser_init,Action,Login_System,flights,vuser_end
MercIniTreeSectionName="Profile Actions"
MercIniTreeFather=""
[RunLogicRunRoot]
RunLogicActionOrder="Action,Login_System,flights"
MercIniTreeFather=""
MercIniTreeSons="Action,Login_System,flights"
RunLogicNumOfIterations="1"
Name="Run"
RunLogicRunMode="Sequential"
RunLogicObjectKind="Group"
RunLogicActionType="VuserRun"
MercIniTreeSectionName="RunLogicRunRoot"
[RunLogicEndRoot]
RunLogicActionOrder="vuser_end"
MercIniTreeFather=""
MercIniTreeSons="vuser_end"
RunLogicNumOfIterations="1"
Name="End"
RunLogicRunMode="Sequential"
RunLogicObjectKind="Group"
RunLogicActionType="VuserEnd"
MercIniTreeSectionName="RunLogicEndRoot"
[RunLogicInitRoot]
RunLogicActionOrder="vuser_init"
MercIniTreeFather=""
MercIniTreeSons="vuser_init"
RunLogicNumOfIterations="1"
Name="Init"
RunLogicRunMode="Sequential"
RunLogicObjectKind="Group"
RunLogicActionType="VuserInit"
MercIniTreeSectionName="RunLogicInitRoot"
Files Generated During Replay
This section describes what occurs when the Vuser is replayed.
The options.txt file is created
The file pre_cci.c is created defined in options.txt
The file logfile.log is created defined in options.txt
The output.txt file is created contains all the output messages of run.
The file Vuser.c is created. contains 'includes' to all the relevant .c and .h
logfile:This file should be empty if there are no problems with the preprocessing stage.
options.txt
-+
-DCCI
-D_IDA_XL
-DWINNT
-IC:\Documents and Settings\weibin\桌面\flithts\practice
-IC:\Program Files\Mercury Interactive\Mercury LoadRunner\include
-ec:\documents and settings\weibin\桌面\flithts\practice\\logfile.log
c:\documents and settings\weibin\桌面\flithts\practice\\combined_practice.c
c:\documents and settings\weibin\桌面\flithts\practice\\pre_cci.c
vugen.dat
This Vugen.dat file resides in the data directory and contains general information about VuGen,
to be used by both the VuGen and Controller.
mdrv.dat
mdrv.dat=execute log
mdrv_cmd:
-usr "C:\Documents and Settings\weibin\桌面\flithts\practice\practice.usr" -qt_result_dir "C:\Documents and Settings\weibin\桌面\flithts\practice\result1" -correlation_files -file "C:\Documents and Settings\weibin\桌面\flithts\practice\practice.ci" -drv_log_file "C:\Documents and Settings\weibin\桌面\flithts\practice\mdrv.log" -product_name vugen -extra_ext vugdbg_ext -cci_elevel -msg_suffix_enable 0 -vugen_win 131670 -vugen_animate_delay 0 -out "C:\Documents and Settings\weibin\桌面\flithts\practice\"
Themdrv.dat(create Vuser type)file contains a separate section for each protocol defining the location of the
library files and driver executables
Calling External Functions
Call functions that are defined in external DLLs
Loading a DLL—Locally
You use thelr_load_dllfunction to load the DLL in your Vuser script.Once the DLL is loaded,
you can call any function defined within the DLL,without having to declare it in your script.
Loading a DLL—Globally
You can load a DLL globally.
Add a list of the DLLs you want to load to the appropriate section of the mdrv.dat file, located in the LoadRunner/dat directory.
Use the following syntax,
PLATFORM_DLLS=my_dll1.dll, my_dll2.dll, ...
replacing the wordPLATFORM.with your specific platform. For a list of platforms, see the beginning section of themdrv.datfile.
