Automated Testing in Workflows

Until now, testing a workflow meant publishing it, opening a user's proxy on the bot, triggering the flow, completing every input and approval by hand, and then checking Reports for errors — once per scenario, and all over again after every fix. Automated Testing replaces that with test cases you define once against a workflow and re-run on demand, so you can validate a workflow before it goes live and re-validate it after every change.

This page introduces the testing section, the test case list, and the test case statuses. The pages that follow cover creating test cases, running test cases and reading reports, and how test cases behave across workflow versions.

The test case list

The testing section lists every test case for the workflow with the following details:

• Test Case Name
• Description
• Created on
• Created by
• Status — Ready to test, Draft, or Error
• Actions — Run test (enabled only when the status is Ready to test), Edit, Duplicate, View report and Delete.
• Report — the execution report for the test case, similar to workflow execution reports.

From here you can also create a test case manually or auto-generate test cases with AI — see Creating test cases.

Test case statuses

• Ready — the test case is fully configured and can be run.
• Draft — the test case is saved but not yet complete.
• Error — at least one node in the test case has an error, typically a mandatory mock value that hasn't been provided. The node in question is flagged, and each configuration screen shows the errors that belong to it so you can fix them screen by screen — Save & Continue is blocked while errors remain.