NexusDB

The CoverageAnalyst tool helps you visually identify the portions of your code that are not fully exercised. With Quality Suite CoverageAnalyst you can build better, more effective test cases.

The most important use of a coverage analyzer is to ensure that all parts of a module (application, DLL, COM object, etc.) have been executed during testing. Far too many programs are released with bugs that escape detection during the quality assurance phase simply because the offending code is never executed. Qality Suite CoverageAnalyst helps to ensure that all parts of the program have been executed.

Project Page

The project page lists the modules (.exe and .dlls) that make up your project. You can include or exclude modules from analysis and view module information.

Routines Page

The Routines page lets you select the routines you want to analyse. Loading an application for analysis causes this page to be populated with data in the format of a routine list.

The routine list can be viewed in a number of different layouts. Choose the desired view from the Layout Selector combo box on the tool panel or from the context menu displayed when you right-click the application area. The following table identifies the available built-in layouts.
 

Module Coverage Page

When the probram being analyzed is terminated, the module coverage is calculated and shown. The module coverage list can be displayed in a number of different layouts.

The following table identifies the available built-in layouts:

Layout
Result

All Source Files
Shows all source files included in the module.

Source Files with 100% Coverage
Shows only the source files where every executable line in all the routines selected for analysis was executed.

Source Files with less than 100%
Shows only the source files where not every executable line in the routines selected for analysis was executed.

Depending on the currently selected layout, the Module Coverage page shows any or all of the following information.

Binary Module: The name of the binary module where this routine resides.

Source Module: The name of the logical source module.

Source file: The name of the current source file. Note that the same source file may be included in multiple modules, and that, depending on the compiler used to build the binary module, a logical module may be built from multiple source files.

Code Lines: The total number of executable source lines in the range of routines selected for tracking. The footer for this column shows the total number of executable source lines tracked in this session.

Lines Hit: The number of lines that were actually executed during this session.

Coverage %: The percentage of code lines that were executed. A coverage percentage of 100 means that all selected lines in the source file were executed.

In addition, some layouts for the Module Coverage page show a Coverage % column as a horizontal bar, whose length represents the percentage value.

Trace Page

The Trace page shows the execution trace of the module being analyzed assuming tracing has been requested. Each source line executed is shown with a time stamp, a thread ID, and location information—that is, the corresponding routine and line number.

Tracing is mainly used for debugging deadlocks. If your application stops responding, running it in the Qality Suite CoverageAnalyst with tracing enabled lets you determine what the last source line executed was for each thread. From that, you can typically determine the cause of the hang quite easily.

Common Tool Features Page

Click the link above to see the common features across all tools.