Running a Try Script Test

If you have implemented your .NET test code you can run a Try Script test from within Microsoft Visual Studio .NET.

  1. Choose one of the following:
    • Press F8.
    • Choose Silk Performer > TryScript.
    The .NET Code is compiled to a .NET assembly.

    A BDF script is generated by the BDL Generation Machine based on the meta information of the custom attributes and the settings in the Options dialog.

    The most recent BDF script is overwritten if there have been changes to the meta data of your assembly (changed custom attributes, changed method order, changed generation options, etc.).

    If the meta data has changed but you have altered the latest BDF file manually, you will be prompted to specify whether or not you wish to have the file overwritten, in which case you will lose recent changes. This detection is achieved by comparing the last modified date of the BDF file with the timestamp scripted in the BDF file.

  2. If you have multiple virtual user classes (classes that have the VirtualUser attribute applied) you will be prompted to specify which of the users is to be started. The test begins.

    If you have the Automatic Start when running a Try Script option selected, TrueLog Explorer will start, loaded with the TrueLog generated by the test.

    Virtual user output is displayed in the Virtual User Output tool window.

    Load test controller output is displayed in a separate pane of the Output tool window.

Once the load test is complete you can explore the other results files (log, output, report, and error) by selecting them from the Silk Performer Results menu.