Chapters

Chapter 7

Validating and testing

Validation checks the structure of the draft. Testing checks how it behaves. Use both before every release.

Validate the draft

Select Validate in the top bar. The report lists every issue, such as a missing entry step, a disconnected step, an invalid branch, an undeclared variable, an incomplete translation, or an action that is not configured. Fix each one and validate again until the report says the draft is ready to publish.

A validation report with no issues.
Figure 18. A validation report with no issues.

Test in the draft playground

Select Test in the top bar. The playground opens in a new browser tab and runs the draft, not the published version.

Test runs never create a customer conversation, and they are not counted in Untrained queries or Observability.

The draft playground with the run trace.
Figure 19. The draft playground with the run trace.

What to test

CaseCheck that
Happy pathThe customer reaches the intended outcome.
Wrong inputThe bot explains the expected format and lets the customer retry.
Empty resultThe bot says nothing was found and offers a next step.
Dependency failureAn API failure follows the Failure branch and offers retry or a person.
FallbackAn unrecognised reply gets the fallback message.
HandoverThe Live Agent step reaches the right department.
LanguageEach enabled language reads correctly.
ChannelThe conversation works in the real web widget or WhatsApp number.
Important

Never build an endless retry loop. After a few failed attempts, change the interaction: show choices, ask for less, or transfer to a person.