Set Control Coupling Options
You can set the options for Control Coupling to build your project in HCL OneTest™ Embedded Studio.
Execute a build with Control Coupling
- In HCL OneTest™ Embedded Studio, open the Settings of the project and click the menu.
- In the right panel, click on the Build options and edit the options by clicking on the … button.
- In the dialog window that shows up on the right, you can select the different tools that can be used for the build. Select Ctrl Coupling analysis to enable the control coupling feature.
Control Coupling options
Options for Control Coupling can be updated in the following menu of the settings:
From this setting page, you can change the following choices:
- Trace file name (.tgf): sets the name of the trace file dedicated to control coupling. By default, this name is the base name of the test with the extension .tgf.
- Exclude libraries: Include or exclude the control couplings that end with a call to a function that is not part of the application (sets the -noccext option of the report generator if it is set to yes).
- Report Template: changes the template of the report generator. By default, this template is ccreport.template.
- Module as: Select the choice that corresponds the best to your definition of a module. A
module can be defined as a function or a compilation unit. HCL OneTest™ Embedded offers
two ways to interpret Control Coupling, depending on how the "module" in CAST-19 is interpreted:
- Module as function: Each call between each function is considered as Control Coupling.
- Module as compilation unit: Only the calls between two functions in two different compilation units are considered as Control Coupling. Moreover, the different called stacks in the calling module are also considered as different Control Couplings. With the previous option set, the user can group two or more compilation units in a single module (called component) in order to ignore the calls between these compilation units.