Coverage Analyzer: FAQ

How do I reset the results for my test group?

Before you start a new test cycle, you should reset the results of your test group or test groups.

You can do that by doing the following:

1. Start transaction SCOV.

2. Choose  Coverage Analyzer  Administration  Reset .

3. Select your test group from the list in field Test Group.

4. Choose Delete Coverage Results of Selected Objects to delete all of the code coverage statistics of your test group.

You can also reset the statistics of selected programs or processing blocks. In the Details Display, select the objects whose statistics should be reset. Then choose the Reset function.

I want to report code coverage by package. How can I do that?

The Details Display presents code coverage in accordance with the settings on the Settings tab that is shown when you choose  Coverage Analyzer  Display  Details .

Choose Package in the Access via frame to have the Details Display aggregate code coverage by development package.

I want to report one result for all packages. Can the Coverage Analyzer aggregate the results of several packages?

The Details Display cannot aggregate the code coverage results of multiple packages.

However, you can use the Global Display to aggregate code coverage across packages. Test group ALL will always show aggregated statistics of the packages reported in the Global Display.

To use the Global Display, you will need to activate recording of code coverage histories. It is also helpful to limit histories to the packages in which you are working.

I would like to automate code coverage reporting. Is there an API for accessing the statistics?

There is currently no publicly available API to the Coverage Analyzer. The ABAP class CL_COVERAGE_ACCESS is for internal use only and may be changed or deleted without warning.

However, a public API is planned for an upcoming release.

When I try to do anything in the Administration section, I get the message 'no authorization'.

To use the Details Display or Global Display, you need only an authorization for transaction SCOV (authorization object S_TCODE, value SCOV for field TCD).

To do any administrative task in the Coverage Analyzer, you will also need an authorization for object S_COV_ADM with value 02 for field ACTVT.

I noticed performance problems after I create a test group.

The Coverage Analyzer records code coverage statistics separately for each test group. You should therefore create as few test groups as possible and never more than 5 test groups in a system.

How often is data collection triggered in the Coverage Analyzer? When was the last data collection?

The Coverage Analyzer announces how long it has been since the last data collection on the transaction entry screen. If the data collection job is running, then you will see a legend such as Last Data Collection 35 Minutes Ago.

By default, the RSCVR_TRIGGER_COLLECT job is scheduled with an automatic repeat interval of 45 minutes. To double-check the repeat interval, see the job details in transaction SM37.

How can I change the frequency of data collection?

In transaction SM37, display the instance of the RSCVR_TRIGGER_COLLECT job that is in the status Scheduled.

Choose  Job  Change  and Start Condition and then Period values to change the job repeat interval.

I don't see any data in the Details Display. Is data collection working?

Check the following:

• In transaction SM37, search for the RSCVR_TRIGGER_COLLECT job. Has the job been completed successfully? Is there a new instance of the job waiting to run (status Released)?

• If the job is terminating abnormally, then you will have to analyze and correct the problem.

• If the job is not scheduled properly, then do the following:

  1. Return to transaction SCOV.

  2. Choose  Coverage Analyzer  Administration  Consistency Checks. 

  3. Mark Check Status of Background Jobs and Repair and run the consistency check.

  4. Switch to  Coverage Analyzer  Administration  Monitor  to see the results of the consistency check. You can also check the status of the RSCVR_TRIGGER_COLLECT job directly, in transaction SM37.

My code under test is executed, but I don't see any coverage results in the Details Display.

Make sure that your code under test really is executed. For example, set a breakpoint in the code before running your tests.

Make sure in transaction SCOV under  Coverage Analyzer  Administration  On/Off, Status  that data collection is activated (the icon in the Exception column is green) in all of the application servers on which your tests will run.

If your tests run on several servers in the system, then you must trigger the data collector manually by executing the ABAP report RSCVR_TRIGGER_COLLECT. Or you can wait for the periodic background job RSCVR_TRIGGER_COLLECT to run before you display the results.

After you have triggered the data collector, it takes a few minutes for the collector to complete before the updated results can be displayed. If you still do not see any code coverage results, then check in transaction SM66_OLD that no Coverage Analyzer tasks are still running.

Note: The Refresh button in the Details Display triggers the data collection only on the server where the button is pushed.

The statistics cover code that I am not interested in.

Filter the results in the Main Choice and Other Filter tabs of the Details Display.

Also make sure that you don't perform any unnecessary tasks with users in your test group. All coverage generated by registered users will be recorded in your test group.