Testing and Debugging the bot

Once the Skills are developed, you should test them before making these available to users. The Bot Testing feature helps to ensure that skill matching, the conversation flow, and fulfillment are working as intended by simulating the user experience.

Testing the Bot

To access Bot Testing, click the Bot Testing icon on the right side Menu This opens the Test Widget. You can test User phrases, Prompts, Rules, Fulfillment, and more through chat with the bot by entering messages and receiving responses.

Debugging your Skills

During testing of Skills, you can leverage the Debug Utility that helps understand any issues that may occur during skill execution. The information about various conversation items of the skill, like the context of the operation, rulesets, and local/global attribute values can be viewed.

The Debug log contains the series of events inside the Bot.

The Debug page displays all the events when a skill is being executed such as the start and end of a conversation flow, success or failure of a message, the response sent, message received, and so on. The following image shows a few events as an example.

For debugging of the Skills with Integration and to know the Web service response and request data, you can click on the event "Operation Executed".

Conversation History

All interactions between users and the bot are captured and available in the Conversation History.
Using the Conversation History, you can understand the details of underlying system events. This is particularly useful when troubleshooting problems that occur with the bot, configured channels, or integrations.

• Select the conversation from the list to view the details in the Conversation Logs section.

• Once the required Conversation is selected from the list, the Conversation log section is populated with Conversation details. The context at each event of the conversation is also provided as part of the events data in the conversation log.

• You can view the details about the execution results of the operation, ruleset, and so on by clicking on the events.

• All the system skills and small talk conversations are also captured as part of conversation history.