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. When configuring your coverage agent, keep in mind that while you can use the coverage agent in single-user mode, it's not recommended for web applications with more than one tester. See Coverage Agents in Multi-User Mode below for more information.
You can confirm that the components in your environment have been connected to coverage agents easily. Open the Manual Testing module where you'll see your systems and their environments, as defined in the Environment Manager, listed alphabetically there. Choose the environment you want and you'll see its components in a table, including the coverage agents they are connected to.
If you need to connect coverage agents to components, or change the ones they're currently connected to, go to the Environment Manager and edit your environment diagram, then do the following:
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.