Testing AI Demo Branches Against the Real Product
Published October 21, 2026 · By Kate Steinmeyer · AI Demo Creation

An AI-generated demo with multiple branches can look coherent while one path reaches a screen that the product cannot reach from its starting state. Test each branch as a separate product claim.
Map every path before polishing
Draw the branch tree with entry condition, actor, action, and result for each path. Mark where branches rejoin. Identify choices that change only the story and choices that require a different permission, plan, or environment.
A path labeled “Admin view” should not show controls available only to an account owner unless the role is explained. A path labeled “Connect an integration” should not imply a live connection if it uses a simulated state.
Replay the paths in the product
For each branch, ask a reviewer to perform the same task in a current environment. Record the version, role, sample data, and outcome. Test the branch labels too: the choice a buyer clicks must lead to the answer promised by its label.
For a hypothetical approvals demo, a requester branch may show submission and status tracking, while a manager branch shows review and decision. The branches should use the same fictional request and agree on its final state.
Check transitions and dead ends
Try every branch from the published entry link. Look for loops, missing back paths, and steps that depend on a choice made in another branch. Ask a first-time viewer to explain what each path proved and what remains untested.
When one branch fails verification, do not assume the others are safe. Record the specific failure, fix the source path, and retest the full tree after the change. The branching guide covers when branching helps the viewer; this test focuses on product fidelity.
Test each branch from its own starting state
A branch test should include its entry condition, expected action, visible state, and exit. For a fictional permissions demo:
| Branch | Expected buyer action | Product reference | Failure to catch |
|---|---|---|---|
| Manager approves | Open pending item, approve | Current manager workflow | Approval appears without the manager role |
| Manager sends back | Request more detail | Current revision workflow | Demo jumps to approved status |
| Requester views result | Open notification | Current requester workflow | Requester sees controls they cannot use |
Click each branch from a fresh starting state rather than testing only the default path. Confirm links, labels, permissions, and the final status. If one branch is simulated, identify it where the choice occurs. A passing branch test means the resulting story is accurate, not merely that every hotspot responds to a click.