Once you have implemented your .NET test code, you can execute a Try Script run from
Microsoft Visual Studio by calling
from the
Silk Performer menu. Try Script runs are trial test runs that you can use to evaluate if your tests have been set up correctly.
The steps that are then performed by the Add-In are as follows:
- The .NET code is compiled into a .NET assembly.
- A BDF script is generated based on the meta information of the custom attributes and the settings in the
Options dialog box.
- The most recent BDF script is overwritten if there have been changes to the meta data of your assembly (for example, changed
custom attributes, method order, or generation options).
- If the meta data has changed, but you have altered the latest BDF file manually, you will be prompted to confirm that you
want to have the file overwritten. This detection is achieved by comparing the last modified date of the BDF file with the
timestamp scripted in the BDF file.
- 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.