Step 3: Creating and Running a Measurement in a Measurement Series

Procedure

To measure code coverage in a measurement series, you simply create measurements in the series. The series orders the measurements (and the results) chronologically in the series.

Here is a code snippet showing how to create and run a measurement in a series.

Syntax Syntax

DATA: measurement TYPE REF TO if_scv_measurement,
      series TYPE REF TO if_scv_series.

* Set the retention interval for raw data if the default 1 week is not okay
series->set_testkey_expiration( cl_scv_expiration=>create( i_weeks = 2 ) ). 

* Create the next measurement in the series
* Measurements that belong to the same set in the series
* can all use the same name (see below)
measurement = series->create_measurement( 'MY_STANDARD_MEASUREMENT' ).

* Start the measurement 
measurement->start( ). 
* Execute test activities, here a harmless CCMS standard report 
SUBMIT rsdssmpl_performance AND RETURN.
measurement->stop( ).

End of the code.

The life cycle of a measurement in a series is like that of a discrete, standalone measurement. That is, you create the measurement, start it to record activity, and so on.

There are differences:

You create the measurement in the series, not directly from the Coverage API factory.
The series applies its default configuration and selection to the measurement, unless you supply your own configuration and/or selection objects.

For more information about result configurations and object selections, see Default Settings.

It is not sensible to have more than one measurement running at a time in a series. Otherwise, the complications defeat the purpose of measurement series, which is to make it easy to create sets of identical, repetitive measurements.

You can have multiple measurement series active at the same time, as long as the users do not overlap while the measurements are active.

Note Note

Do you have a standalone measurement that you would like to add to a series? No problem, you can assign the measurement to a series.

End of the note.

Continue to calculate code coverage results.

Here is the complete tutorial program.