Configuring coverage settings in Design Studio
About this task
To configure coverage settings in Design Studio complete the following steps:
Procedure
-
Select your map in the workspace and click the Coverage
Settings icon in the toolbar, or select the Coverage
settings option from the menu.
Note: If an <map>.mcs.json file does not already exist, the system creates a new one with default settings.
-
Define one or more coverage runs.
- Right-click the CoverageRuns parent node and click Add to add a new coverage run.
- For each coverage run, provide a unique identifier in the Coverage Identifier field.
-
Optional: Select Keep or
Skip to determine whether the engine includes
or ignores the specific coverage run during execution.
Note: Coverage IDs marked as Skip are not considered during execution and will not be displayed in the coverage settings report tab.
- Specify the required input and output overrides for each run. Only overridden input and output cards are saved in the .mcs.json file.
-
Specify the source map locations. To add a source map location, right-click the
SourceMaps parent node and click
Add. You must specify source map locations to resolve
binary engine map rules into readable source map rules for the final
report.
Note: You can right-click the CoverageRuns or SourceMaps parent nodes at any time to access additional options, such as Delete, Restore Defaults, and Expand All.
-
Set the Report level for the final output. The default
report level is Details. You can also select Outline or
Verbose.
Note: To generate map coverage reports at the Details or Verbose level, ensure that the map source (.mms) and map debug (.mdg) files are located in the specified directory. These files are required to resolve binary engine map rules into a readable format for the final report.
- Set the OnRunError behavior. You can choose Continue or Stop. The default setting is Stop to ensure that map execution halts if an exception occurs, which provides immediate failure visibility.
-
Click Save to apply your changes and update the
<map_name>.mcs.json file.
When you click Save, the system performs a validation check. This check ensures that there are no duplicate coverage identifiers, no empty source map locations, and no empty file paths for your overridden input and output cards.