Control Coupling Report

The default Control Coupling report is in HTML format. It is generated from a template named ccreport.template provided as text file that you can modify to customize the report. It uses 4 online JavaScript libraries:
  • Bootstrap,
  • JQuery,
  • Font Awesome,
  • VisJS.
These libraries are not provided. You need an internet connectivity when you open the report. If not, download the libraries (.css and .js files), copy them in the same folder than your report, and modify the template file as follows:
Replace the following lines:
<link rel="stylesheet" href="" integrity="sha384-MCw98/SFnGE8fJT3GXwEOngsV7Zt27NXFoaoApmYm81iuXoPkFOJwJ8ERdknLPMO" crossorigin="anonymous">
<link rel="stylesheet" href="" integrity="sha384-B4dIYHKNBt8Bc12p+WXckhzcICo0wtJAoU8YZTY5qE0Id1GSseTk6S+L3BlXeVIU" crossorigin="anonymous">
<link rel="stylesheet" href="">
<script src="" integrity="sha384-q8i/X+965DzO0rT7abK41JStQIAqVgRVzpbzo5smXKp4YfRvH+8abtTE1Pi6jizo" crossorigin="anonymous"></script>
<script src="" integrity="sha384-ZMP7rVo3mIykV+2+9J3UJ46jBk0WLaUAdn689aCwoqbBJiSnjAK/l8WvCWPIPm49" crossorigin="anonymous"></script>
<script src="" integrity="sha384-ChfqqxuZUCnJSK3+MXmPNIyE6ZbWh2IMqE241rYiqJxyMiZ6OW/JmZQ5stwEULTy" crossorigin="anonymous"></script>
<script src=""></script>
With the following ones:
<link rel="stylesheet" href="./bootstrap.min.css>
<link rel="stylesheet" href="./all.css">
<link rel="stylesheet" href="./vis.min.css">
<script src="./jquery-3.3.1.slim.min.js"></script>
<script src="./popper.min.js"></script>
<script src="./bootstrap.min.js"></script>
<script src="./vis.js"></script

The Control Coupling report is made of three parts.


The Summary table displays the following information:
  • The number of Control Couplings of your application, given the information you provided.
  • The percentage of Control Couplings that have been covered, i.e. executed by at least one test case.


The Details table lists all the Control Couplings and displays for each of them the following information:
  • The calling module.
  • The control flow, i.e. the successive calls in the module that end with the external call in the called module. Note that the called module is mentioned in the last function of the control flow.
  • A check mark if it is a longest Control Flow.
  • A check mark if it is a shortest Control Flow.
  • The list of test cases that covered this control flow. If the Control Coupling feature has been set with the unit testing feature, the test cases are the one in the .ptu files named as <service>/<test>.
  • • The associated requirements. If the Control Coupling feature has been set with the unit testing feature, the requirements are those that have been described in the .ptu files with the keyword REQUIREMENT for each test cases that covered this Control Coupling.
  • • A check mark if the control coupling has been covered.

Call Graph

The Call Graph part displays all the functions as an interactive call graph from left to right or from top to bottom, depending on the selector button position on the top of the call graph.

You can select a control coupling in the table to highlight it in the call graph.


Filters can be applied in the report with different buttons at the top:
  • You can choose first to display all Control Couplings, the longest (only the Control Couplings that have the longest control flow in the calling module) or the shortest (only the Control Couplings that have the shortest control flow in the calling module). The summary tables and the details table are updated accordingly to your selection.
  • You can also select the calling modules and the called modules. It filters the Control Couplings depending on their calling and called modules. The summary tables and the details table are updated accordingly to your selection.