...

dottestcli.exe -config "builtin://Collect Static Coverage" -solution SOLUTION_PATH

The location of the static_coverage.xml file will be printed to the console.

...

1. Add the monitor task or goal to your build command and execute the command in the AUT's main directory to generate the monitor.zip package. The location of the package will be printed to the console.
   

   Maven

   Code Block
   mvn package jtest:monitor

   Gradle

   Code Block
   gradle assemble jtest-monitor -I [INSTALL]/integration/gradle/init.gradle

   Ant

   Code Block
   ant -lib [INSTALL]/integration/ant/jtest-ant-plugin.jar -listener com.parasoft.Listener jtest-monitor

   Info
   Ant requires all classes to be compiled before the monitor task is executed. Modify your project prior to the build and configure the task to ensure the correct sequence. The following example shows how the target can be configured: <target name="jtest-monitor" depends="compile">              <jtest:monitor/> </target>

    
   The location of the monitor.zip package that contains the static_coverage.xml file will be printed to the console.

2. Extract the contents of the monitor.zip package to the server machine.

...

1. Open CAM in a browser:

   Code Block
   http://[your-Tomcat-host:port]/cam.

2. Click Agents.
   
   
3. Click Add Connection to configure the connection with the Coverage Agent.
   Agent Name: Any user-friendly string that you want to display in CAM (for example, the name of the application).
   Agent Address: The URL of the server where the Coverage Agent is attached to the AUT (see Step 2). The default port number for the Coverage Agent is 8050.
4. Click Test to verify the connection.
   
5. Click Connect after successfully testing the connection.

...

...

Connecting SOAtest to the Coverage Agent

The connection to the coverage agent is handled through a SOAtest test configuration.

...

The -publish option is required to send the merged coverage data to DTP. Alternatively, you can configure the report.dtp.publish=true option in the .properties file where you configure dotTEST or Jtest.

Collecting Application Coverage from Multiple Users

...

with CAM

CAM allows you to You can collect coverage information for multiple users that are simultaneously accessing the same Java or IIS web application server. This allows QA engineers to perform parallel testing sessions and associate coverage with individual users.

...

1. Configure the Coverage Agent to enable the multiplemulti-user mode; see Configuring the Coverage Agent to Run in the Multiple-User Mode.
2. Specify your User ID for the connection with the Coverage Agent attached to the AUT. This will enable the Coverage Agent to identify and assign coverage information to individual users who are simultaneously interacting with the AUT.
   - If you use SOAtest, provide your User ID on the Application Coverage tab of your test configuration; see Connecting SOAtest to the Coverage Agent.
   - If you use CAM, add your User ID to the HTTP request header of the browser you will use to interact with the tested web application and then provide the same User ID when connecting CAM to the Coverage Agent; see Specifying User ID for Testing with CAM.

...

1. .
2. Add your User ID to the HTTP request header of the browser you will use to interact with the tested web application
3. Provide your User ID when connecting CAM to the Coverage Agent.

Configuring the Coverage Agent

Enabling the Multi-user Mode with dot TEST

...

You can enable the multi-user mode by modifying the invocation of the dotTEST IIS Manager tool (see Step 2: Attach the Coverage Agent to the Application Under Test (AUT)). Launch the tool with the -multiuser switch:

Code Block
dottest_iismanager.exe -multiuser

Enabling the

...

Multi-user Mode with Jtest

You can enable the multiplemulti-user mode by modifying the options in the the agent.properties file, which is included in the monitor.zip package (see Generating Static Coverage with Jtest). Open the file and configure the following option:

jtest.agent.enableMultiuserCoverage=true

...

Adding the User ID to the HTTP header

Modify the the HTTP request header of your browser by configuring the Test-Operator-ID option with a unique User ID. This will enable the Coverage Agent attached to the AUT to identify and assign coverage information to individual users who are simultaneously interacting with the AUT.

A convenient way to add a Test-Operator-ID is to install one of the browser plugins that allow you to easily modify HTTP headers. The following example shows a Test-Operator-ID specified in Chrome with the ModHeader plugin.

Connecting CAM to the Coverage Agent in the

...

Multi-user Mode

Provide your User ID when connecting CAM to the Coverage Agent (see Step 3: Connect CAM or SOAtest to the Coverage Agent). The User ID must be identical to the Test-Operator-ID provided to your browser.

Testing in the

...

Multi-user Mode

Perform testing sessions, download the results, and mergee the coverage data, as described in steps 4-7 above. When downloading the results from CAM, ensure that the Session Tag field is completed with a tag unique to each user. We recommend that the session tag include the User ID.

...