Code Tab

Code view displays generated code files for the current test scenario. The following code types are available:

Client Proxy Code

The Client Proxy tab displays generated WebClient proxy code. When loading a WSDL file to access a Web Service, a WebClient proxy class is created. Proxy classes are created on method and type information in WSDL files. When Web Service methods return complex types, additional classes are declared. These additional classes are used to represent the complex types in the method calls that take complex parameters. For detailed information about WebClient Proxy generation, consult the MSDN for details regarding WSDL.EXE, a tool that creates proxy classes in the same way.

Test Driver Code

The test driver Test Code tab displays code generated for the test driver. This code can be compiled to a standalone console application. The main method for the application contains the calls to the test cases that are defined in your current test scenario. The test case methods contain all the calls that you have defined in your scenario for the respective test case.

When you export a standalone console application (via the Export menu) and then run the application, you will see output information regarding successful/failed methods in the console window.

Silk Performer .NET Framework Code

The Silk Performer .NET Framework tab displays test code for Silk Performer .NET Framework. For each test case in your current test scenario you will find a method with the [Transaction] attribute applied to it. These transaction methods contain all the calls that you have defined in your test scenario for the respective test case.

This code can either be exported to Microsoft Visual Studio as a Silk Performer .NET Project, or it can be exported directly to Silk Performer. In either case, results will be reported to Silk Performer and can be viewed in the log files or virtual user output.

Native BDL Script

The BDL Native tab displays native BDL script for Web Service calls. When testing Web Services, .NET Explorer can create BDL scripts with WebPagePost API calls for each Web Service method call in the current test scenario. WebPagePost methods are called with posted HTTP traffic from .NET Explorer during the last execution of the current test scenario.

Exporting to a native BDL script allows you to test a Web Service by sending its HTTP traffic without using the .NET Framework to generate the HTTP traffic.

BDL for .NET Framework

Th BDL FW tab displays BDL script for Silk Performer .NET Framework. When exporting a project as a Silk Performer .NET Framework project, .NET Explorer uses the code in the Silk Performer .NET Framework code pane, compiles the code to a .NET Assembly (DLL), and creates a BDL script that loads the DLL and calls the methods that have been marked with the [Transaction] attribute. The BDL script is shown here, but it is not shown in the final state that will be generated upon export. Only a skeletal BDL script is displayed.