In order for CTP to gather coverage information related to your manual tests, you will need to configure the components in your environment to use one of your deployed application coverage agents. This section assumes that you have already configured coverage agents for the application under test (AUT) using Parasoft dotTEST or Jtest (the recommended method), or using one of the command line coverage tools shipped with SOAtest or CTP that you can use to analyze application binaries when you don't have access to the project's source code. If you have not, please see Configuring the Application Under Test for Coverage for more information.
You can confirm that the components in your environment have been connected to coverage agents easily. Open the Environment Manager and edit your environment diagram. Click the Coverage Agents tab and you will see a convenient table organized by component name that includes coverage agent, build ID, and DTP project information for each, as applicable.
If you find a component that needs to be connected to a coverage agent but is not, go back to the Diagram tab to configure that connection:
If you have multiple testers working on a web application at the same time, it is recommended that you run your coverage agents in multi-user mode. When a component in an environment is configured to a coverage agent running in single-user mode, you will only be able to run one test at a time in that environment. How you run your coverage agent in multi-user mode depends on which coverage agents you're using.
jtest.agent.enableMultiuserCoverage and jtest.agent.autoloadMultiuserLibs are enabled in the agent.properties.jtest.agent.enableMultiuserCoverage is enabled, jtest-otel-ext.jar and opentelemetry-javaagent.jar will be automatically loaded from the agent.jar directory. All three are included in the coverage agent download and should be deployed to the same directory when the coverage agent is installed.agent_client.exe -multiuser.See Application Coverage for more information about configuring coverage agents.
Regardless of which coverage agent you are using, each tester's browser needs to be set up to inject the following HTTP header (where <USER> is the tester's CTP username): baggage: test-operator-id=<USER>
If this header is not injected, you will not capture any coverage data. You can inject this header using a browser extension.
If you want CTP to be able to report on manual tests that have been impacted by code changes, you need to configure your coverage agents with the location of your application under test so that, when changes are made to it, it will be able to determine what classes changed. How you do this depends on which coverage agents you're using.
jtest.agent.appLocationIncludes and (if applicable) jtest.agent.appLocationExcludes in the agent.properties file and configure them appropriately. See Jtest Coverage Agent settings for more information about Jtest coverage agent parameters.-appLocationInclude <PATH_TO_APPLICATION>: Required. Specifies the location of application files for the application being tested manually. Use multiple arguments to specify multiple locations, if necessary (for example, when application files do not all reside in the same directory).-appLocationExclude <PATH_TO_APPLICATION>: Optional, but recommended. Specifies the location of files that are within a directory indicated in an -appLocationInclude argument but do not need to be considered when determining what manual tests are impacted by code changes. Excluding these files can greatly decrease the time needed to analyze files for changes. Use multiple arguments to specify multiple locations.