SOAtest and Virtualize with CTP 2020.1
Page tree

Versions Compared

Old Version 1

changes.mady.by.user Adam Trujillo

Saved on

compared with

New Version Current

changes.mady.by.user Adam Trujillo

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space FUNCTDEV and version SVC2020.1

 In this section:

Table of Contents
maxLevel1

Overview

The test impact analysis (TIA) functionality analyzes the coverage data for your the application under test and outputs a .lst file indicating which tests generates a list of tests that have been affected by changes to since the application. You can pass the previous build. The list of tests are saved to a .lst file that you can pass as a resource to the SOAtest command line so that it can run interface. SOAtest will only the subset of tests affected identified by change TIA in order to validate the changes. In this section:

Table of Contents
maxLevel1

Overview

Test impact analysis is intended to be implemented as part of an automated process. The following overview describes the test impact analysis process: 

  1. Configuration: Configure the coverage agent (agent.jar) shipped with SOAtest, attach it to your AUT, and enable SOAtest to communicate with the agent.  
  2. Collect information about what test cases cover: Run your full test suite so that the agent can collect data about the tests and the code they cover.
  3. Generate a baseline coverage report: Process the data collected by the agent to create a baseline report.  
  4. Generate the .lst file containing the tests affected by changes: When a new version of the application is available, run the TestImpactAnalysis script  script to process the baseline coverage report. A .lst file containing the tests affected by change will be created.
  5. Run the tests affected by change: Deploy the latest version of the application (.war) to your server and run a job that executes SOAtest using the .lst file as the input to verify the changes.   

Configuration

TIA is intended to be implemented as part of an automated process. Perform the following steps to enable TIA.

...

jtest.agent.associateTestsWithCoverageEnables/disables associating coverage with particular tests; the default value is false.
jtest.agent.runtimeDataSpecifies a location on the application server for the agent to store the coverage data it collects at runtime. 
jtest.agent.includes

A comma-separated list of patterns that specify classes to be instrumented. The following wildcards are supported:

* matches zero or more characters
** matches multiple directory levels

In the following example, all classes from the com.myapp.data package and all classes from package and subpackages that start with com.myapp.common will be instrumented:

com/myapp/data/*,com/myapp/common/**

jtest.agent.excludes

A comma-separated list of patterns that specify classes to be excluded from instrumentation. The following wildcards are supported:

* matches zero or more characters
** matches multiple directory levels

In the following example, all classes from the com.myapp.transport package and all classes from package and subpackages that start with com.myapp.autogen will be excluded from instrumentation:

com/myapp/transport/*,com/myapp/autogen/**

jtest.agent.autostartEnables/disables automatic runtime data collection; the default is true.
jtest.agent.port Sets up agent communication port; the default is 8050.
jtest.agent.debug Enables/disables verbose output to console; the default is false.
jtest.agent.collectTestCoverage Enables/disables collecting coverage information for test cases. The ; the default value is false .
jtest.agent.enableMultiuserCoverage 

Enables/disables collecting web application coverage for multiple users; the default value is false. 

jtest.agent.serverEnabledActivates the agent.

...