The coverage analysis process consists of the following three stages:

Compiling

The first stage is to compile applications with Insure++ and build their coverage analysis database, usually named tca.map.

insure++.coverage_boolean [on|off]

If set to on, the only data that will be stored is whether or not each block was executed. If off, the number of times each block was executed is also recorded. Setting this option to on will cause your program to compile and run slightly faster.

insure++.coverage_map_data [on|off]

If set to on, coverage analysis data is collected whenever applications are compiled. Such applications are then candidates for collecting coverage analysis data at runtime. Setting this option to off disables this. Applications must be compiled with this option on before the runtime coverage analysis options have any effect.

insure++.coverage_map_file [filename]

Specifies the name of the file to which the coverage analysis database will be written. Filenames may be specified using any of the standard methods that make sense at compile time (see Filenames). For example, you cannot use %p or %D with this option. If this option is not specified, the default filename tca.map is used.

Running Test Cases

The next stage is to run test cases against applications that have been compiled with coverage analysis enabled, which creates entries in the TCA log file, usually named tca.log.

insure++.coverage_banner [on|off]

If set to on, a message is displayed at runtime indicating the file to which coverage analysis data will be written. Setting this to off disables this message.

insure++.coverage_log_data [on|off]

If set to on, coverage analysis data is collected whenever applications which have been compiled for coverage analysis are executed. Setting this option to off disables this.

insure++.coverage_log_file [filename]

Specifies the name of the file to which coverage analysis data will be written. Filenames may be specified using any of the standard methods. Refer to Filenames for appropriate specification methods. If this option is not specified, the default filename tca.log is used.

insure++.coverage_overwrite [on|off]

Indicates how data from successive application runs will be merged with any existing data. If set to on, the existing log file will be overwritten each time the application runs. If this is turned off, then each run causes new data to be added to the existing log file to form a new, combined result. In this mode, the log file data will still be discarded if the executable has changed since the last recorded log data.

insure++.coverage_switches switches

Specifies the command line arguments to be passed to the tca command when it is executed as a result of a summarize coverage option.

Running TCA

The last stage is to run the tca analysis tool to view the coverage analysis results. 

registertool TCA version

Used for internal maintenance. This option should not be modified.

tca.password arg1 arg2 arg3 (Unix)

Used for internal maintenance. This option should not be added or modified by hand. Licenses should be managed with pslic.