Once the Skills are developed, you should test them before making these available to users. The Bot Testing The Test Bot gives an option to test the skills developed before making them available to the end-users. This feature helps to ensure that skill matching, the conversation flow, and fulfillment execution are working as intended by simulating the user experience.
Testing the Bot
To access Bot Testing, click the Test Bot Testing icon as shown belowicon on the right side of the Bot Builder. This opens the Test Widget. You can test user the User phrases, Prompts, promptsMessages, rulesRules, fulfillmentIntegrations, and more through chat with the bot by entering messages and receiving responses directly in the Bot Builder interface.
. This ensures that the Bot identifies the Skill correctly and the intended action such as integration, transformation is executed correctly.
Debugging your Skills
During testing of When testing Skills, you can leverage the Debug Utility that helps understand to troubleshoot any issues that may occur during skill execution. The Here, the information about various conversation items of the skill, like such as 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 triggered during skill execution 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"
Debug logs can be viewed while Skill is being executed in Test Bot. To view logs, follow the below steps:
Open Test Widget.
Click on the Debug button to open the testing panel.
Start a conversation with the bot by entering the user phrases.
| Info |
|---|
Debug logs can available until the testing panel is open. Once closed, the testing panel is reset. You can now view the Debug logs in Conversation History. |
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 to troubleshoot conversations when errors occur during skill execution. To view the conversation logs:
Navigate to Conversation History under Bot Menu.
Apply the required filters and select the conversation from the list.
The Conversation log section is populated with Conversation details. The context at each event of the conversation is available as part of the event data.
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.
Below is the list of entities captured as part of the logs:
Icon | Description | Purpose | |
|---|---|---|---|
| 1 | 
| Attribute | Attribute details such as Attribute name, Assignment type, Scope and value assigned are captured |
| 2 | 
| Integration : Connections to external systems to perform actions for fulfilling the user's request involves integration. | Details of the request sent to the external web service and the response received are captured |
| 3 | 
| Information message | User messages and Bot responses sent during skill execution |
| 4 | 
| Automation Integration | Details of Automation Workflow included in the skill conversation flow and process status. |
| 5 | 
| RuleSet | The rule executed, value and evaluation status is captured |
| 6 | 
| Set Attributes | Information regarding the attributes used, transformations applied and values assigned. |