Test and troubleshoot your solution

• Save the current draft.
• Use fictional test data.
• Define the expected outcome before each test.
• Prepare happy-path, incomplete and invalid examples.
• Identify every important branch.
• Confirm the expected worker-response structure.
• Reset conversational state between independent scenarios.
• Record the project version being tested.
• Avoid testing production actions from a draft environment.

Enlarge

Enlarge

Reset chat

Clears the current test conversation so an independent scenario does not inherit earlier context.

Suggested messages

Quick starting examples. They are not a complete test set.

Message input

Accepts the test request.

• The user enters an open customer question.
• The worker identifies a likely late-delivery intent.
• The response includes structured routing information.
• The result names the process intended to handle the request.
• The exact fields shown are specific to this demonstration.

1. 1Open the worker in Composer.
2. 2Select the Test panel.
3. 3Select Reset chat.
4. 4Enter one test message.
5. 5Compare the returned result with the expected contract.
6. 6Confirm the detected intent.
7. 7Confirm extracted values and uncertainty handling.
8. 8Confirm that the worker does not attempt the deterministic resolution itself.
9. 9Repeat the test with alternative wording.
10. 10Test a missing-information request.
11. 11Test an unsupported request.
12. 12Reset the chat before each independent scenario.

Enlarge

• Initial content and instructions
• Buttons and structured choices
• Open-text input
• Required fields
• Validation messages
• Worker routing
• Called flows
• Completion messages
• Fallback behaviour

1. 1Save the current draft.
2. 2Open Run Demo.
3. 3Begin with the main happy path.
4. 4Complete each displayed input.
5. 5Confirm the expected next step appears.
6. 6Complete the entire journey.
7. 7Restart the interaction.
8. 8Test an alternative branch.
9. 9Test missing or invalid data.
10. 10Test an open-text request that invokes the worker.
11. 11Confirm that the correct deterministic flow starts.
12. 12Repeat until every important route has been covered.

1. Test the worker directly
       ↓
2. Test the Agentic Worker step in the flow
       ↓
3. Test the complete process from Run Demo

Stage 1: Worker

Confirm that the request produces the expected intent and structured fields.

Stage 2: Flow integration

Confirm that the Agentic Worker step passes the correct input and that the following branch receives the expected result.

Stage 3: End-to-end process

Confirm that the customer request starts the intended deterministic resolution flow and completes successfully.

1. 1Enter “Where is my package?” in the worker Test panel.
2. 2Confirm the worker returns a late-delivery classification.
3. 3Enter equivalent wording in the customer-facing Run Demo.
4. 4Confirm the main flow invokes the router.
5. 5Confirm the late-delivery branch starts.
6. 6Confirm the deterministic resolution requests the required information.

Enlarge

Enlarge

1. 1Save the current project.
2. 2Note the displayed issue count.
3. 3Inspect recently added or changed steps.
4. 4Confirm that every required field has a value.
5. 5Confirm that referenced workers, flows and tools are available.
6. 6Check that process steps have the required incoming and outgoing connections.
7. 7Check branch outcomes and destinations.
8. 8Confirm that expected variables are present.
9. 9Run Demo again.
10. 10Continue to the readiness check after the issue is resolved.

Enlarge

• A successful result states that Designer found no issues.
• The summary may show cards and step counts.
• Let’s go continues toward publishing or deployment.
• A successful technical result should be combined with business testing.

1. 1Resolve the current issue count.
2. 2Save the draft.
3. 3Run each priority test.
4. 4Record the test result.
5. 5Continue toward deployment.
6. 6Review the readiness result.
7. 7Return to the Editor if a blocking issue remains.
8. 8Continue only after both technical validation and business review succeed.

The next stage is covered in the Publishing and deployment guide.

Reproduce
   ↓
Change one thing
   ↓
Save
   ↓
Run the failed scenario
   ↓
Run a nearby successful scenario
   ↓
Run validation
   ↓
Save as version

1. 1Reproduce the problem before changing the design.
2. 2Make one focused correction.
3. 3Save the draft.
4. 4Repeat the failed test.
5. 5Repeat at least one related passing test.
6. 6Check that the correction did not break another branch.
7. 7Run the readiness check.
8. 8Save a meaningful version when the correction is accepted.

• Expected results were defined before testing.
• Only fictional test data was used.
• The worker was tested directly.
• Independent worker tests used Reset chat.
• The happy path completed successfully.
• Alternative wording was tested.
• Missing information was tested.
• Invalid input was tested.
• Ambiguous requests were tested.
• Unsupported requests followed the approved fallback.
• Important branch boundaries were tested.
• Worker output matched the flow contract.
• Called flows started correctly.
• Human approval paths were considered.
• The visible issue count was resolved.
• A readiness check completed successfully.
• Business acceptance was recorded separately.
• The accepted project state was saved as a version.