Workflow Branch Test Coverage

How to use Workflow Branch Test Coverage

A workflow can have test records while leaving a branch untested. Keep ordered node-path evidence and unmatched scenarios visible before a human accepts the real automation.

1. Declare each intended branch and its exact ordered node labels.
2. Paste actual test-record paths and explicit pass, fail or unrun statuses.
3. Run missing or incorrect branches in your real workflow and retain evidence before accepting the exported coverage register.

Good to know

• Conditions, expressions and workflow code are never executed. Labels and recorded statuses are unverified declarations.
• A matching recorded pass counts coverage, but failed, unrun, unknown and mismatched records still hold the overall review.
• Each input field is limited to 8,000 UTF-16 characters and each exact-header CSV to 100 data rows. Quoted commas/newlines and doubled quotes are supported. Unsupported controls and unpaired surrogates are refused. Decimal magnitudes are at most 999,999,999 with a smallest nonzero magnitude of 0.000000001; exponents are refused and whole counts are checked exactly. Rational results show at most 18 fractional digits and an ellipsis when more remain.
• Editable Markdown and long-form CSV both retain all summary metrics, context, detailed findings, entered source rows and scope limitations. CSV columns are Record type,Section,Source row,Field,Value; spreadsheet-looking text is apostrophe-prefixed. These are review artifacts, not proof of source truth or a completed real-world task.
• Runs deterministically in this browser. No AI, API, vendor connection, upload, outreach, calendar change, payment, storage or background monitoring. Use authorized pseudonymous records; inspect exports before sharing.