Introduction

You can connect CTP component instances to application coverage agents as part of the Parasoft Application Coverage solution. After doing so, notifications regarding coverage agent connectivity will be displayed on the environment diagram in CTP. For complete information about using the Application Coverage solution, refer to the Collecting Coverage for Web Applications guide.

Be aware that the number of coverage agents you can have connected to CTP is determined by your license. See Installing and Running CTP for more information about your license and how many coverage agents it allows. If you need to remove coverage agents from a component instance, see Removing a Coverage Agent from a Component.

Before you can connect a CTP component to a coverage agent, you need to configure the application under test (AUT) using Parasoft dotTEST or Jtest (the recommended method), or one of the command line coverage tools shipped with SOAtest or CTP that you can use to analyze application binaries if you don't have access to the project's source code. For more information about configuring the AUT using dotTEST or Jtest, see the documentation for those tools at docs.parasoft.com. For more information about using the command line coverage tools that ship with SOAtest or CTP, see Application Coverage for SOAtest and Collecting Coverage for Microservices Guide for CTP. The coverage tools shipped with CTP can be found in <TOMCAT-DIR>\webapps\em\coverage.

Once CTP has been connected to a coverage agent, data is published to DTP using the REST API or, in the case of manual testing, when stopping a manual test session. You can even publish test data from non-Parasoft testing frameworks using the REST API. You can then use the REST API to define a baseline build and query Test Impact Analysis using DTP data in CTP and take advantage of CTP's ability to aggregate impacted tests across multiple DTP projects within an environment. Go to Help (question mark icon) > API Documentation or open a browser window to http://<HOST>/em/apidoc and scroll down to the "Coverage" section to use the REST API.

Connecting a CTP Component to a Coverage Agent

To connect a CTP component to a coverage agent:

1. Either create a new Component Instance for the desired component or edit an existing one. For more information, see Adding Component Instances or Modifying a Component Instance's Settings.
2. With component instances that are connected to a coverage agent, it is recommended that you include the coverage agent as part of the Name and/or Description.
3. Click Coverage and choose a Connection type:
   • Agent-initiated (WebSocket): Choose this option if you want your coverage agent to register itself with CTP. Choose your coverage agent type (Java or .NET) and you will be given properties for the ctp.websocket.url and the ctp.subscription.queue that you need to add to your agent properties file (agent.properties for Java or agent.config.json for .NET); you can copy the settings directly from here. See Application Coverage for more information about configuring coverage agents.
     
     

     If you want to edit other agent.properties or agent.config.json files without needing to come to this dialog for each component, you can reuse the settings for ctp.websocket.url and ctp.subscription.queue, just replace the environment ID and component ID with the values for the new component in the latter. You can find those values easily by clicking the component in your diagram and checking the URL field in your browser.

   • CTP-initiated (HTTPS): Choose this option if you want CTP to register the coverage agent. Enter the URL where the application under test and coverage agent are hosted in the Agent URL field, making sure to include the protocol (HTTP/HTTPS) and port number of the agent. To test the connection to the coverage agent, click Test Connection. Note that when the connection is successfully tested, the remaining settings are automatically populated with default values from the agent.
     
4. CTP will automatically use the default DTP settings provided by your coverage agent. You do not need to configure these settings unless you want to override the defaults from the coverage agent; only enter values in these fields if you want to override the coverage agent's settings. If you choose to override one or more of them, be aware of the following:
   • DTP Project: This value must match the dtp.project value set for dotTEST or Jtest when collecting the static and dynamic coverage files. Multiple components can publish to the same DTP project. CTP will generate a unique session tag for each component when publishing coverage to DTP based on the session tag provided in the REST API and the component name to ensure that coverage data from multiple components published to the same project in DTP will be merged.
   • Filter: Specify a filter for this coverage agent. Filters are provided by the DTP server and associate tests in DTP, which will help identify tests affected by a test impact analysis. The field will autocomplete as you enter text. You cannot create filters from here; if there is a filter you want that is not available, go to DTP and create it there.
   • Build ID: Set to the build ID with which to correlate coverage results. If you want to merge SOAtest coverage results with results from other types of testing—such as unit testing and manual testing of the same application—they must all use the same build ID. The build ID set here must match the build ID set for dotTEST or Jtest when collecting the static and dynamic coverage files and uploading the coverage data.
   • Coverage images: Specify a set of tags that are used to create coverage images in DTP. A coverage image is a unique identifier for aggregating coverage data from runs with the same build ID. Separate multiple entries with a semi-colon ( ; ). For details, see the Parasoft DTP user guide.
     
5. Click Finish.

Note: You will need to update these DTP settings when a new version of your application is deployed. You can do this either in this dialog or in the agent's properties file (agent.properties or agent.config.json); the settings will be updated automatically the next time the agent is started.

Removing a Coverage Agent from a Component

When a component has a coverage agent connected to it, a small icon will appear in the environment diagram.

To remove the coverage agent, you can do either of the following:

• Edit the component instance (see Modifying a Component Instance's Settings), click on the Coverage tab, then delete coverage agent URL from the Agent URL field.
• Delete the component.

Coverage Agents Table

You can review all of your components and which coverage agents they are connected to in a convenient table. While in edit mode for the environment, click the Coverage Agents tab to view it. The table is organized by component name and includes relevant information regarding coverage agent, build ID, DTP project and filter, and coverage image for each.