...
- Generating the static coverage file. When you have access to the application source code, the static coverage file should be generated by Jtest in .xml or .data format as this method comes with several advantages over the alternative. You can also generate the static coverage file by analyzing the application binaries using the coverage tool shipped with Selenic when you do not have access to the application source code. See Generating the Static Coverage File below for more information.
- Attaching the coverage agent to the application under test (AUT). The coverage agent ships with Selenic and allows you to monitor the code being executed when the AUT is running.
- Configuring Selenic to connect to the coverage agent and collect runtime coverage and upload the data to DTPcoverage.
- Executing tests with Selenic as part of an automated process.
- Creating a Coverage Report and Uploading the Data to DTP.
- Reviewing the application coverage on DTP in the Coverage Explorer.
...
Info |
---|
The |
Code Block | ||
---|---|---|
| ||
# === LICENSE === # === END USER LICENSE AGREEMENT === # Set to true to accept the Parasoft End User License Agreement (EULA). # Please review the EULA.txt file included in the product installation directory. parasoft.eula.accepted=true # === NETWORK LICENSE === # Enables network license - be sure to configure DTP server settings. selenic.license.use_network=true selenic.license.network.edition=custom_edition selenic.license.custom_edition_features=Automation, Publish to DTP, Test Impact Analysis # === DTP SERVER SETTINGS === # Specifies URL of the DTP server in the form https://host[:port][/context-path] #dtp.url=https://localhost:8443 # Specifies user name for DTP server authentication. #dtp.user=admin # Specifies password for DTP server authentication - use java -jar selenic_analyzer.jar -encodepass <PASSWORD> to encode the password, if needed. #dtp.password=admin # Specifies name of the DTP project - this setting is optional. #dtp.project=[DTP Project Name] # === DTP REPORTING === # Enables reporting test results to DTP server - be sure to configure DTP server settings. #report.dtp.publish=true # Specifies a build identifier used to label results. It may be unique for each build # but may also label more than one test sessions that were executed during a specified build. #build.id=${dtp_project}-yyyy-MM-dd # Specifies a tag which represents an unique identifier for the run, used to distinguish it from similar runs. # It could be constructed as minimal combination of following variables that will make it unique or specified manually. # e.g. ${config_name}-${project_module}-${scontrol_branch}-${exec_env} #session.tag=[tag] # Specifies a set of tags that will be used to create coverage images in DTP server. # Coverage images allow you to track different types of coverage, such as coverage for unit, functional, manual tests and others. # There is a set of predefined tags that will be automatically recognized by DTP, see the examples below. # You can also specify other tags that will be used to create coverage images. #report.coverage.images=${dtp_project} #report.coverage.images=${dtp_project};${dtp_project}_Unit Test #report.coverage.images=${dtp_project};${dtp_project}_Functional Test #report.coverage.images=${dtp_project};${dtp_project}_Manual Test # === CONSOLE VERBOSITY LEVEL === # Increases console verbosity level to high. #console.verbosity.level=high |
...
Run your tests in command line mode using Selenic agent and analyzer settings file you have configured (see Configuring Selenic to Collect and Upload Coverage). This step should be part of an automated process. Coverage data will be collected as tests execute. A coverage report can be created and, if publishing to DTP has been enabled, uploaded to DTP using the coverage tool shipped with Selenic.
Reviewing Coverage in DTP
...