Test the path before you change the work.
Simulate your workflow to validate how it performs, where it may break, and what needs human review.
- The five objects. People, information, tasks, approvals and tools. A legend, not navigation.
- The six steps. Request received, details entered, manager review, approved, work scheduled, client notified. Diagram nodes, never controls.
This page explains what a workflow test covers. It does not run one. There is no simulation engine behind it, nothing is computed, and no result on this page is a measurement of anything.
Run test: Not yet available. There is no simulation engine behind this page, so there is nothing to run and no result to show. The artwork shows what a finished run would look like.
Path Plan
Test the path before you change the work.
Simulate your workflow to validate how it performs, where it may break, and what needs human review.
- The five objects. People, information, tasks, approvals and tools. A legend, not navigation.
- The six steps. Request received, details entered, manager review, approved, work scheduled, client notified. Diagram nodes, never controls.
This page explains what a workflow test covers. It does not run one. There is no simulation engine behind it, nothing is computed, and no result on this page is a measurement of anything.
- Not yet available. There is no simulation engine behind this page, so there is nothing to run and no result to show. The artwork shows what a finished run would look like.
- Return to the map
Simulation controls
Step 1
The scenario a test would be given before it runs.
- Test case name. For example, New Client Onboarding Test.
- Trigger data. For example, an intake form submission.
- Role assignments. The artwork paints this control with no options in it.
- Approval response. The artwork paints this control with no options in it.
- Tool availability. The artwork paints this control with no options in it.
- Exception scenario. The artwork paints this control with no options in it. The five run modes the sources name are listed on the canvas below instead.
Four of the six controls on this plate are dropdowns with nothing in them. This build does not invent an option list, so they are listed here as the artwork shows them and no selector is offered.
Step 1
Simulation controls
The scenario a test would be given before it runs.
- Test case name. For example, New Client Onboarding Test.
- Trigger data. For example, an intake form submission.
- Role assignments. The artwork paints this control with no options in it.
- Approval response. The artwork paints this control with no options in it.
- Tool availability. The artwork paints this control with no options in it.
- Exception scenario. The artwork paints this control with no options in it. The five run modes the sources name are listed on the canvas below instead.
Four of the six controls on this plate are dropdowns with nothing in them. This build does not invent an option list, so they are listed here as the artwork shows them and no selector is offered.
Interactive path canvas
Step 2
The five scenarios a test would step through, and the playback the artwork paints beneath them.
- Happy path.
- Approval rejected.
- Missing information.
- Owner unavailable.
- Tool failure.
The five scenario names are the run modes the design sources define, so they ship as written. The playback controls beneath them drive a simulation that does not exist, so each one is disabled with its reason beside it. Speed would change only the visualisation even if there were one.
Play: Not yet available. The artwork paints this control with no options in it, and this build does not invent a list.
Pause: Not yet available. The artwork paints this control with no options in it, and this build does not invent a list.
Step back: Not yet available. The artwork paints this control with no options in it, and this build does not invent a list.
Step forward: Not yet available. The artwork paints this control with no options in it, and this build does not invent a list.
Reset: Not yet available. The artwork paints this control with no options in it, and this build does not invent a list.
Playback speed: Not yet available. The artwork paints this control with no options in it, and this build does not invent a list.
No scenario selected. Selecting one describes what that run would look for; it does not run anything.
Step 2
Interactive path canvas
The five scenarios a test would step through, and the playback the artwork paints beneath them.
- Happy path.
- Approval rejected.
- Missing information.
- Owner unavailable.
- Tool failure.
The five scenario names are the run modes the design sources define, so they ship as written. The playback controls beneath them drive a simulation that does not exist, so each one is disabled with its reason beside it. Speed would change only the visualisation even if there were one.
- Not yet available. The artwork paints this control with no options in it, and this build does not invent a list.
- Not yet available. The artwork paints this control with no options in it, and this build does not invent a list.
- Not yet available. The artwork paints this control with no options in it, and this build does not invent a list.
- Not yet available. The artwork paints this control with no options in it, and this build does not invent a list.
- Not yet available. The artwork paints this control with no options in it, and this build does not invent a list.
- Not yet available. The artwork paints this control with no options in it, and this build does not invent a list.
Event log, results, issues and replay
Steps 3 to 6
What a finished run would report. Every value on this plate is painted TBD.
- Event log. Step, owner, input, decision, output and status, for each of the six steps. Every cell but the step name is painted empty.
- Completion status. TBD.
- Total time. TBD.
- Handoffs. TBD.
- Manual updates. TBD.
- Exceptions found. TBD.
- Issues identified. No issues identified in this scenario, because no scenario was run.
These are not results. They are the shape a result would take. No number here is a measurement and none is published as fact.
Replay from start: Not yet available. There is no run to replay, because nothing runs on this page.
Replay from selection: Not yet available. There is no run to replay, because nothing runs on this page.
Steps 3 to 6
Event log, results, issues and replay
What a finished run would report. Every value on this plate is painted TBD.
- Event log. Step, owner, input, decision, output and status, for each of the six steps. Every cell but the step name is painted empty.
- Completion status. TBD.
- Total time. TBD.
- Handoffs. TBD.
- Manual updates. TBD.
- Exceptions found. TBD.
- Issues identified. No issues identified in this scenario, because no scenario was run.
These are not results. They are the shape a result would take. No number here is a measurement and none is published as fact.
- Not yet available. There is no run to replay, because nothing runs on this page.
- Not yet available. There is no run to replay, because nothing runs on this page.
Human review required
Simulation results require human review before saving.
The sentence above is painted into the artwork and ships verbatim. It is the honest part of this band. The control beside it would let a visitor mark their own review complete, with no reviewer identity, no evidence statement and no record, so it ships disabled.
Mark review complete: Not yet available. Marking a review complete records who reviewed what, and against which evidence. There is no review record, no reviewer identity and no audit trail, so this cannot be done honestly here.
Human review required
Simulation results require human review before saving.
The sentence above is painted into the artwork and ships verbatim. It is the honest part of this band. The control beside it would let a visitor mark their own review complete, with no reviewer identity, no evidence statement and no record, so it ships disabled.
- Not yet available. Marking a review complete records who reviewed what, and against which evidence. There is no review record, no reviewer identity and no audit trail, so this cannot be done honestly here.
Compare paths
Step 7
Three columns a comparison would set side by side, and the six factors it would compare on.
- Current (as built).
- Test run (this simulation).
- Recommended (pending review).
- Factors. Flow steps, handoffs, approvals, manual updates, exceptions and tool dependency.
Comparison is a section of this page, not a page of its own. The three columns are read-only and no value in them has been measured.
Step 7
Compare paths
Three columns a comparison would set side by side, and the six factors it would compare on.
- Current (as built).
- Test run (this simulation).
- Recommended (pending review).
- Factors. Flow steps, handoffs, approvals, manual updates, exceptions and tool dependency.
Comparison is a section of this page, not a page of its own. The three columns are read-only and no value in them has been measured.
What you can do with a test
Three controls are painted here. Two of them promise storage that does not exist; the third is re-pointed at the page that does reach a person.
Nothing on this page is saved. Nothing is written back to a map. Nothing is sent to Quill by pressing a button here.
Save test result: Not yet available. Test results are not stored. Nothing you do on this page is saved, sent to Quill or written to any map.
Update map: Not yet available. There is no map of yours to write to, and this build will not claim to have changed one.
What you can do with a test
Three controls are painted here. Two of them promise storage that does not exist; the third is re-pointed at the page that does reach a person.
Nothing on this page is saved. Nothing is written back to a map. Nothing is sent to Quill by pressing a button here.
- Not yet available. Test results are not stored. Nothing you do on this page is saved, sent to Quill or written to any map.
- Not yet available. There is no map of yours to write to, and this build will not claim to have changed one.
- Take this to the intake — the artwork paints Send Test to Quill; nothing is sent from this page
Questions about testing a path
Six questions are painted on this plate. No answer is painted for any of them, and none is invented here.
- What is a workflow test? No answer has been supplied.
- What do the results tell me? No answer has been supplied.
- Do tests change my map? No answer has been supplied.
- Who should review the results? No answer has been supplied.
- What happens after I send it to Quill? No answer has been supplied. Nothing is sent from this page in any case.
- Can I run multiple scenarios? No answer has been supplied.
Questions about testing a path
Six questions are painted on this plate. No answer is painted for any of them, and none is invented here.
- What is a workflow test? No answer has been supplied.
- What do the results tell me? No answer has been supplied.
- Do tests change my map? No answer has been supplied.
- Who should review the results? No answer has been supplied.
- What happens after I send it to Quill? No answer has been supplied. Nothing is sent from this page in any case.
- Can I run multiple scenarios? No answer has been supplied.
Where this page goes next
This is the Test the Path workspace of the Path Plan family. The System Simulation page is its sibling from a different approved package, and the two share one implementation rather than each having a simulator of their own.
- Test how the system works. The System Simulation package: the six-step player, the scenario setup and the event log, as approved by QP-MAP-001. Same components, different plates.
- Review the map with Quill. What a map review covers, and how to ask for one.
To verify before this page claims it
The supplied artwork paints figures, dates, names, statuses and statements that this build has not been able to confirm. Nothing on this list is published as fact until Quill confirms it.
- Completion status, total time, handoffs, manual updates and exceptions found, all painted TBD.
- Every cell of the painted six-row event log, which is empty apart from the step names.
- The answers to all six painted questions, none of which is supplied.
Corrected in the live text
The artwork is published exactly as supplied. Where it paints a misspelling, a wrong number or a state nobody chose, the live text beside it reads correctly.
- The artwork paints SEND TEST TO QUILL as a primary control implying a completed send. It is re-pointed at the built intake and relabelled to a navigation verb, so it cannot read as a claim that anything was sent.
- The artwork paints a SAVE & EXIT control in its navigation band. The band is cropped and the control is not rebuilt.
What the sources do not carry
These are gaps in the supplied material, not decisions. They are recorded here so a reader can see why a control is disabled rather than guessing.
- There is no simulation engine, so no run, replay, playback or result is possible.
- Four scenario dropdowns are painted with no options in them and no option list is invented.
- There is no review record, so a review cannot be marked complete by anyone.
- There is no store, so a test result cannot be saved and no map can be updated.
- No answer text exists for any of the six questions painted on section 08.
Where this goes next
Every one of these is a page that exists today. Nothing here points at a route that has not been built.
Map the work beneath the work
Clarity today. Better systems tomorrow. Tell us what should work better and we will map the work before anyone builds anything.
Review with Quill
A human review of a map or a blueprint is requested, not scheduled here. Submitting a request asks Quill to review and respond. It does not approve scope, authorise payment, begin implementation or confirm timing.
Review the Map with Quill explains what a review covers and how to ask for one. It does not book, confirm or schedule a review: there is no calendar behind it and no availability has been verified. Talk to Quill reaches a person today.