Demo Branch Test Coverage

How to use Demo Branch Test Coverage

An interactive sales demo can have a working happy path while an important customer branch remains untested. Reconcile your graph with actual recorded test paths before a handoff.

1. Describe the current demo as stable nodes and transitions and mark actual required branches.
2. Enter recorded, ordered test paths with the exact current version and an approved terminal node.
3. Test the missing branches in the real demo and resolve impossible, stale or incomplete runs before delivery.

Good to know

• Only complete, contiguous, same-version paths from the approved start to a declared terminal credit coverage. An incomplete run does not silently count as a passed branch test.
• Cycles are traversed with bounded reachability, not executed. Reachable nonterminal nodes without outgoing transitions are reported separately. No browser session or conversion is verified.
• Each input field is limited to 8,000 UTF-16 characters. CSV needs the exact displayed header and at most 100 data rows. Quoted commas, doubled quotes and quoted newlines are supported. Duplicate identities are refused unless the tool explicitly reports them as findings.
• Markdown and CSV are editable review artifacts, not certificates. Spreadsheet-like text is apostrophe-prefixed in CSV to reduce formula execution risk; check the actual importer before sharing. Decimal ratios are rounded to at most 12 places.
• Runs only on the records you enter, locally in your browser. No AI call, provider connection, account inspection, upload, automatic outreach or saved input. Use neutral identifiers rather than personal or secret content.