Steps Performed by the Add-On before Try Script Runs

The .NET add-on performs the following steps before it begins with the execution of a Try Script run:
  1. The add-on compiles the .NET Assembly. If the compilation fails the add-on does not execute the Try Script.
  2. The Code Generation Engine generates the BDF/BDH files.
    The engine checks if it has to overwrite old BDF/BDH files. Old files are overwritten only if there has been one of the following changes made to the structure of the .NET test driver:
    • Changes to VirtualUser, Transaction, TestMethod, TestAttribute, or BdlParameter attributes.
    • Changes to the sequence of a method definition.
    • Changes to the parameter definition of the methods.
    • Changes to code generation options.
    If significant changes have been made, the engine checks whether the BDF has been changed manually since it was last generated. If it has been changed, you must specify whether the file can be overwritten. If you select No, the Try Script is not executed.
  3. The add-on prompts you to execute the VirtualUser. If there is more than one VirtualUser class in the .NET test driver, you must choose which virtual user is to be executed.
  4. A temporary project file is generated and configured to run the Try Script.
  5. The Virtual User Output window is activated.
  6. The test begins.
  7. If the Automatically Start TrueLog Explorer option setting has been enabled, TrueLog Explorer will launch with the TrueLog of the active Try Script.
  8. All virtual user output, contingent on options, is printed to the Virtual User Output window.
Parent topic: Try Script Runs