PLSQL Test Coverage Tool

The PLSQL Test Coverage tool enables the collection and display of code coverage data on PLSQL stored procedure source code bases of arbitrary size. It is a member of SD's family of Test Coverage tools.

PLSQL Test Coverage Features

  • Dialects: PLSQL 10g and 11g (older dialects on request)
  • Works with arbitrary subsets of source code base
  • Can accumulate data from multiple test runs into one or more test coverage vector (TCV) files
  • Can handles tens of thousands of source files
  • Extremely low probe overhead
  • Operations to combine test coverage data (TCV files) for unions, deltas, intersections
  • Produces coverage report by nested package and internal subroutines/functions.
  • Test coverage collection can run on platform separate from Test Coverage Tool

The PLSQL Test Coverage Tool has an intuitively simply graphical display. It shows

  • Eligible test coverage vector (TCV) result files
  • Selected/accumulated/computed TCV files
  • List of files being tested for coverage
  • Locations of probe points in files
  • Browsable source text of file of current interest
  • Covered/uncovered status of each probe point on file source text
  • Summary statistics for percentage covered

Here is a screenshot (in a popup window) of the PLSQL Test Coverage Display. If you have popups disabled, try this link: screen shot. The example shows test coverage data from a single TCV file. Green intervals in the program text pane illustrate portions of code that were covered by the tests recorded in the TCV file; red intervals indicate those that were not covered. The yellow interval is the selected probe, which you can see from the color key beside the probe in the browser indicates an uncovered portion. Multiple TCV files, each representing distinct collections of usage data, may be overlaid in the display to indicate aggregated test coverage.

Download an evaluation copy

Semantic Designs also offers other PLSQL tools.

For more information: info@semanticdesigns.com    Follow us at Twitter: @SemanticDesigns

PLSQL Test Coverage