RSI Logo
Google
Reactis: Model-Based Testing and Validation
 
 Reactis User's Guide   Contents  |  Index
 Chapters:  1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20

Chapter 10  The Reactis Coverage-Report Browser

The Coverage-Report Browser enables users to view detailed coverage information related to testing and to export the reports in HTML format for viewing and printing within a web browser. Figure 10.1 contains an annotated screen shot of the Coverage-Report Browser. The title bar includes information describing the test suite, tests, and test steps that were exercised before computing the coverage information. Here, the report describes coverage attained after executing steps 1 through 50 of test 11 in test suite cruise.rst. When a report reflects the coverage attained by executing an entire test suite, only the test suite name appears in the title bar.


Figure 10.1: The Coverage-Report Browser.

10.1  Labeled Window Items

  1. The model hierarchy panel works much as the hierarchy panel does in the main Simulator window. Namely, it displays the subsystems that make up the model and how they are related. Clicking the + to the left a subsystem name displays the child subsystems of the item. Clicking on a name causes coverage information for the subsystem to be displayed in the panels to the right. Double-clicking on a name causes the subsystem diagram to be displayed in the Simulator main panel.
  2. This panel displays summary coverage statistics for the subsystem currently selected in the hierarchy panel.
  3. This panel shows coverage information for each child subsystem of the subsystem currently selected in the hierarchy panel. The information is presented as a matrix and includes a row for each child. The first column includes the names of the children, while each subsequent column includes statistics for one of the coverage measures tracked by Reactis. In Figure 10.1, the entry “(6) 83%” indicates that child subsystem DesiredSpeed has 6 branches, 83% of which have been covered. Double-clicking on a row causes the child to become the current subsystem displayed in the Coverage-Report Browser.

    The rows of the table may be sorted based on the values of any column. To cause the values in a particular column to order the rows, the user simply clicks on the header of the column. Clicking once sorts in increasing order of the column entries, while clicking a second time sorts in decreasing order.

  4. For each coverage target in the subsystem currently selected in the hierarchy panel that is not MC/DC-related, this panel displays whether or not the target has been covered. If it has been covered, the test and step in which it was first exercised are also displayed. Double clicking on a row causes the selected target to be highlighted in yellow in the main panel of the Simulator window.

    Targets in the MC/DC-related criteria (decision, condition, MC/DC) are not listed as described above. Instead the list includes an entry for each decision included in the MC/DC criterion. Right clicking on such an entry will activate a pop-up menu that includes the menu item Show Details. When this menu item is selected a dialog conveying coverage information similar to that shown in Figure 7.7 will appear. See Section 7.5.2 for a description of this dialog.

    The rows of the table may be sorted based on the values of any column. To cause the values in a particular column to order the rows, the user simply clicks on the header of the column. Clicking once sorts in increasing order of the column entries, while clicking a second time sorts in decreasing order.

10.2  Menus

Report menu.
The Report menu contains the following entries.
Export...
Invoke the dialog shown in Figure 10.2 that enables the user to export the coverage report in HTML format. See Section 10.3 for details.
Exit.
Exit the Coverage-Report Browser.
Help menu.
The Help menu contains the following entries.
Contents.
Go to the table of contents in the on-line documentation.
Index.
Go to the index in the on-line documentation.
Coverage-Report Browser.
Display Coverage-Report Browser help.

10.3  Exporting Coverage Reports

The Coverage-Report Browser includes a facility that enables users to export coverage reports in HTML format. The resulting files may be viewed and printed using facilities in a web browser. The dialog shown in Figure 10.2 is invoked by selecting the Report -> Export... menu item from the Coverage-Report Browser menu bar. Coverage details in the exported reports are organized so that each subsystem of the model has a section in the report; a subsystem's section includes coverage information for the targets in that subsystem.


Figure 10.2: The dialog for exporting coverage reports in HTML format.

The labeled items in the dialog are used as follows.

  1. The radio button selected from this group specifies the portion of the model which will be included in the exported report.
  2. When this check box is selected, a table of contents containing a link to each section will be included at the top the exported report.
  3. When this check box is selected, for each subsystem a table will be included that gives summary coverage statistics for every child of the subsystem.
  4. When this check box is selected, for each subsystem a table will be included that includes a row for every coverage target in the subsystem. Each row will also include the coverage criterion to which the target belongs, whether or not the target has been covered, and if covered the test and step in which it was first covered.
  5. When this check box is selected, for each Decision a table will be included that gives the coverage details for MC/DC coverage.
  6. When this check box is selected, for every 1d or 2d lookup table a table will be included that shows for every interval in the table the test and step in which it was first covered.
  7. When this check box is selected, the date the report was generated is included at the top of the report.
  8. When this check box is selected, the full operating system paths to the relevant .mdl file and .rst file are included at the top of the report. The .mdl file contains the model from which the report was generated. If the report conveys statistics after tests from a test suite have been executed, then the .rst file named is the file in which these tests reside.
  9. Click this button to display on-line help for the coverage export.
  10. Click this button to preview the report to be exported.
  11. Click this button to export the report. A file selection dialog will appear to allow you to name the file where the report should be written.
  12. Click this button to abort report generation.