Test a workflow
Try a workflow with a dry run that costs nothing, or a live test on real systems, before your team relies on it.
On this page
Testing shows you exactly how a run would move through a workflow: which steps run, which branch a decision takes, where it waits for a person and what it costs. Test a new workflow, or a draft with changes, before applying it.
Dry run or live test
| Dry run | Live test | |
|---|---|---|
| What runs | Every step, with notifications, webhooks and delivery mocked | Every step, for real |
| Leaves Duun | Nothing | Messages, webhook calls and pull requests happen |
| Cost | $0 | Uses credits |
Start with a dry run. Use a live test when you need to see a real pull request or a real Slack message.
Run a test
- Open the factory, select Workflows and pick the workflow. If you have unapplied changes, the test uses your draft.
- Select Test in the toolbar.
- Choose Dry run or Live test.
- Pick an Input sample. Choose a recent issue, the webhook trigger’s sample payload or Manual run (no input).
- Optionally use Force outcome on a decision to test a specific branch. Auto lets the decision run normally.
- Select Start dry run or Start live test.
Watch it run
Each step in the graph lights up as it runs, with its time and cost. The chat pane turns into a transcript showing what each step did, such as “Would post to #platform: Plan ready”.
When the test reaches a step that needs a person, it waits and shows Needs you with options to approve or send it back. Sending it back follows the step’s failure rule, so you can test retries too.
The toolbar shows progress, like “Testing… 4/7 · $0.42”. Select Stop to end the test early; nothing after that point runs.
Read the result
At the end you get a summary: the path the run took, total time, cost and any failures. Select Open as run to see it as a normal run page.
If the test passes, apply your changes. If a step failed, select it in the graph to see why, fix it in the inspector and test again.
If something goes wrong
- Test is disabled. The workflow has problems to fix. Select the change bar to see them.
- A decision always takes the same branch. Try Force outcome to check the other branches work, then improve the decision’s question.
- A live test posted somewhere you didn’t expect. Live tests are real. Use a test Slack channel and a test repo while you’re building.
For more on test modes and forced outcomes, read Test runs.