Overview
Map coverage is a testing and quality assurance feature in IBM Sterling Transformation Extender that identifies executed and unexecuted map rules by applying varied inputs as overrides. The map coverage feature ensures that the map runs in test mode using defined input files and displays the results in a readable format.
You can use map coverage to determine how much of your code paths are executed by the provided inputs. The process identifies fully covered, partially covered, and unexecuted functional maps, as well as execution counts and run map rules.
Map coverage benefits
Integration maps often contain conditional logic, alternate routing paths, and
functional maps that are triggered only by specific input conditions. Without
coverage analysis, it is difficult to verify whether edge-case logic has been
tested. Map coverage addresses this by providing the following benefits:
- Identifies unexecuted map rules in executable and functional maps so you can close testing gaps.
- Reports executed and unexecuted run maps and functional maps to provide visibility into branch coverage across the full map hierarchy.
- Tracks execution counts per rule so you can evaluate how frequently each path is exercised.
- Generates a final, audit-ready JSON report that serves as evidence of test thoroughness.