Test a Workflow
Ask the code assistant to first inspect the workflow’s test sync plan. This is a
checklist of the business scenarios that are already covered and those that still need
tests. For each missing scenario, the assistant will choose an appropriate data
approach.
| Approach | Description |
|---|---|
| Record now | Safely run the scenario once and save the returned data for later replay. |
| Record later | Create the test now and wait until you can supply safe data or access. |
| Reuse a baseline | Reuse recorded data from a similar test. |
| Use generated data | Prepare safe, coherent test data when live recording isn't appropriate. |
After the tests are ready, the assistant runs the affected test and then the focused workflow suite. It should tell you how many tests passed, link the report, and explain any next step in natural language.
Identify Good Workflow Scenarios
Describe business cases, not node names. Here's a useful starter set.
- A normal successful request.
- An empty or “no matches found” result.
- A missing required input.
- A validation or service-error path.
- An out-of-scope request, if the assistant has scope limits.
- Each important create, update, or delete path—using safe test records.