Enabling Code Analysis for Execution Plans

To enable code analysis for an execution plan:

In the menu, click Execution Planning > Details View.
In the Execution tree, select an execution plan.
Click the Deployment tab.
In the Code Analysis Settings section of the Deployment page, click Edit. The Edit Code Analysis Settings dialog box displays.
Check the Enable code analysis check box.
Select a profile from the Code Analysis Profile list box.
In the Hostnames field, enter a comma-separated list of host names, with port, if default port 19129 is not used, from which code analysis information is to be gathered.
For example labmachine1, labmachine2:8000, 198.68.0.1. For each execution plan, you need to define the host names of the machine resources where the AUT is running. For example, with a client/server system, you must not only gather code coverage information on the client, which probably runs directly on an execution server, but also on the server, which likely runs on a different machine. This applies to all multi-tiered applications.

Note: For JUnit code analysis runs, you do not need to specify a hostname.
Click OK to save your settings.

Note: Once code analysis has been defined for an execution plan, each future run of that execution plan will gather code coverage information from the defined host names. While monitoring an execution on the Activities page, you will see that after gathering the sources for tests, Silk Central gathers full code coverage information before beginning test runs. The Code Coverage Controller, which is integrated into each Silk Central execution server, controls all defined hosts during execution runs. For each test of an execution plan, the controller starts and stops all associated instances, collects XML-based code coverage files for the test, and merges the results into a single file. The test then saves the merged code coverage file to its execution results.