Coverity Aquires Kalistick: The new Coverity Test Advisor - QA Edition includes the Cockpit and Recorder.
Skip to end of metadata
Go to start of metadata

Documentation for previous releases

Icon

This is the documentation related to the latest release of Recorder: 7.2. Go to Recorder Archives page to find documentation related to previous releases.

 

The Recorder is the tool that records the execution of functional tests. See the Overview for an architectural view of the Recorder.

Introduction

The Recorder must be installed within the same network as the tested application (usually on a QA/test server, see Installation). It collects information about the execution of each test and uploads it to the Test Advisor Cockpit server. The analysis of this information is done by the Test Advisor Cockpit.

The Recorder is composed of the following components:

  • A lightweight Agent that collects execution data about the tested application.
  • A Scanner that generates an archive with all the files that make up the tested application.
  • A Controller that provides a Web interface and a Web API that you can use to monitor executed tests and the status of the Agent and Scanner.

The Test Advisor Agent works with any Java application (>= 5.0) or .NET application (>= .NET 2.0). It uses dynamic instrumentation to collect data from an application. It does not require any change in application code or in the compilation process. It is only necessary to modify the startup command for your application.

The Scanner is used to scan the files used by your application. By keeping a footprint of each file used by the runtime of your application, The Test Advisor platform detects changes between each version of your application. Note that the Scanner works on runtime files and not on source files.

How it works

The following figure describes the overall behavior of the Recorder:

1. Application scanning
The Scanner is launched each time a new version of the application is deployed on the test server. The Scanner generates a .kss file, called an appscan, which is the footprint of the files that make up the application runtime. The Scanner can be launched manually or integrated into an existing deployment process.

2. Test recording
The Test Advisor Agent records execution footprints of tests that the test team is running. It associates the executed code with each test, line by line, which allows you to see the impact of changing any line of code.

3. Upload to the Test Advisor Cockpit server
The Controller retrieves data files generated by the Scanner and the Agent. The Controller is responsible for uploading these files to the Test Advisor Cockpit server.

General prerequisites

  • Application must be implemented in Java 5.0+ or .NET 2.0+
  • Application must be compiled with debug options
  • No labels