Show TOC

Activating History Recording and Creating New History Versions in the Coverage AnalyzerLocate this document in the navigation structure

Procedure

You can activate or deactivate the history function of the Coverage Analyzer in the Switch Data Aggregation from Different Remote Systems On/Off frame.

A history aggregates Coverage Analyzer statistics to the level of the packages in the system. You view histories in the Global Display. They give you a fast overview of code coverage in the packages in which your company is developing.

By periodically creating new histories, you can compare code coverages from different periods of time and easily analyze trends in code coverage.

The Detail button shows you the history versions in your system and how often the history job runs.

To start history recording or create a new history version, do the following:

  1. Decide which development packages you would like to include in the history. By default, a history includes all packages except those for local (non-transportable) objects. You should specify only the packages in which you are developing or testing.

    Specify your selection of packages in Start of the navigation path Coverage Analyzer Next navigation step Administration Next navigation step Settings End of the navigation path in the Packages Included When History is First Created frame.

  2. Back on the Start of the navigation path Coverage Analyzer Next navigation step Administration Next navigation step On/Off, Status End of the navigation path screen, press the On button in the Switch Automatic Recording On/Off frame.

  3. In the popup window which follows, fill out these fields:

    • Create New Version: Mark this field if you would like to close any previous history that was being recorded and start a new history. The new history aggregates data from now until the next time you create a new history version. The system will ask you for a name for the new history.

      If you leave this field unmarked, then new data is simply added to the existing history.

    • Start Date: Enter the date and time at which the history aggregation job RSCVR_BUILD_GLOBAL_VIEW should start running.

      Be sure to pick a time at least a few minutes in the future. Otherwise, the background processing system may not release the job to run. In this case, the Coverage Analyzer will report a problem scheduling the job. In general if you receive this message, you can use the Consistency Checks to clear the problem automatically.

    • Recording Period: With this field, you determine how often the history job runs. You also determine the granularity of the history. Each run of the job adds a new record to the history. If you choose a period of 1 day, then the job will run once daily and the history will show you daily aggregated values.

      SAP recommends a period of once a day or once every 12 hours. You can space the job runs more closely if you record histories only for a few packages or if you have few test groups.

    You must also mark one of the application servers in the table at the bottom of the window. The history job will be scheduled to run on this server.

You can display histories in the Global Display. Switching history recording on or off has no effect on the Detail Display.