Headless Code Coverage

Generating code coverage in headless mode using the collector
To run code coverage in headless mode using the code coverage collector, start the collector and run the application with settings specified to connect to the code coverage daemon. The daemon listens on one or more ports, waiting for incoming code coverage sessions.
Generating code coverage in headless mode using Remote Debug Service
To run code coverage in headless mode using Remote Debug Service, ensure that Remote Debug Service is started and configured with code coverage collection options, and the settings of the application are specified to connect to Remote Debug Service.
Specifying code coverage options in the startup key
When you run code coverage in the Eclipse IDE or in headless mode, code coverage options can be directly specified in the startup key. In the case of the Eclipse IDE, this allows the user to specify code coverage options prior to the creation of an Incoming Debug Session launch configuration. If the launch configuration already exists, then the startup key options override any settings in the launch configuration. In the case of headless mode, specifying startup key options allows the user to override daemon settings.
Filtering code coverage results during collection
You can use filters to include or exclude modules, parts or compile units, and files during code coverage collection.

Parent topic: Code Coverage