Test an automation before you publish it
Run it against a real past response, force the paths nobody has taken yet, and see exactly where it goes.
Testing is not optional here, and that is deliberate. The On switch will not move until every step has been seen working at least once, because the alternative is finding out from a customer who got the wrong email.
Running a test
- 1Click Test in the automation header.
- 2Pick a real past response to test against — you get a list with the date and a preview so you can find the right one.
- 3Press "Run the test".
The canvas lights up the path it took. Each step shows what it received, what it produced, and how long it took. Nothing leaves the building: no emails are sent, no records are changed, nothing is pushed to your other apps.
Testing the path nobody has taken
The interesting branch is usually the one you have no example of. Use "Change an answer" to override an answer in the test — put a big number in the budget question and watch the high-value branch light up. That way you can prove every path works before the first real response goes down it.
Steps that were skipped
A step that did not run because its branch was not taken is shown as skipped, not failed. Skipped steps still count as untested, which is why the switch keeps asking for more tests until you have covered each path.
If it refuses to turn on, it names the steps it has never seen work. Run a test that reaches those steps and try again.
Was this article helpful?