GETTING STARTED
Kore.ai XO Platform
Virtual Assistants Overview
Natural Language Processing (NLP)
Concepts and Terminology
Quick Start Guide
Accessing the Platform
Navigating the Kore.ai XO Platform
Building a Virtual Assistant
Help & Learning Resources
Release Notes
Current Version
Recent Updates
Previous Versions
Deprecations
Request a Feature
CONCEPTS
Design
Storyboard
Overview
FAQs
Conversation Designer
Overview
Dialog Tasks
Mock Scenes
Dialog Tasks
Overview
Navigate Dialog Tasks
Build Dialog Tasks
Node Types
Overview
Intent Node
Dialog Node
Dynamic Intent Node
GenAI Node
GenAI Prompt
Entity Node
Form Node
Confirmation Node
Message Nodes
Logic Node
Bot Action Node
Service Node
Webhook Node
Script Node
Process Node
Agent Transfer
Node Connections
Node Connections Setup
Sub-Intent Scoping
Entity Types
Entity Rules
User Prompts or Messages
Voice Call Properties
Knowledge AI
Introduction
Knowledge Graph
Introduction
Terminology
Build a Knowledge Graph
Manage FAQs
Knowledge Extraction
Import or Export Knowledge Graph
Prepare Data for Import
Importing Knowledge Graph
Exporting Knowledge Graph
Auto-Generate Knowledge Graph
Knowledge Graph Analysis
Answer from Documents
Alert Tasks
Small Talk
Digital Skills
Overview
Digital Forms
Digital Views
Introduction
Widgets
Panels
Session and Context Variables
Context Object
Intent Discovery
Train
NLP Optimization
ML Engine
Overview
Model Validation
FM Engine
KG Engine
Traits Engine
Ranking and Resolver
Training Validations
NLP Configurations
NLP Guidelines
LLM and Generative AI
Introduction
LLM Integration
Kore.ai XO GPT Module
Prompts & Requests Library
Co-Pilot Features
Dynamic Conversations Features
Intelligence
Introduction
Event Handlers
Contextual Memory
Contextual Intents
Interruption Management
Multi-intent Detection
Amending Entities
Default Conversations
Conversation Driven Dialog Builder
Sentinment Management
Tone Analysis
Default Standard Responses
Ignore Words & Field Memory
Test & Debug
Overview
Talk to Bot
Utterance Testing
Batch Testing
Conversation Testing
Conversation Testing Overview
Create a Test Suite
Test Editor
Test Case Assertion
Test Case Execution Summary
Glossary
Health and Monitoring
NLP Health
Flow Health
Integrations
Actions
Actions Overview
Asana
Configure
Templates
Azure OpenAI
Configure
Templates
BambooHR
Configure
Templates
Bitly
Configure
Templates
Confluence
Configure
Templates
DHL
Configure
Templates
Freshdesk
Configure
Templates
Freshservice
Configure
Templates
Google Maps
Configure
Templates
Here
Configure
Templates
HubSpot
Configure
Templates
JIRA
Configure
Templates
Microsoft Graph
Configure
Templates
Open AI
Configure
Templates
Salesforce
Configure
Templates
ServiceNow
Configure
Templates
Stripe
Configure
Templates
Shopify
Configure
Templates
Twilio
Configure
Templates
Zendesk
Configure
Templates
Agents
Agent Transfer Overview
Custom (BotKit)
Drift
Genesys
Intercom
NiceInContact
NiceInContact(User Hub)
Salesforce
ServiceNow
Configure Tokyo and Lower versions
Configure Utah and Higher versions
Unblu
External NLU Adapters
Overview
Dialogflow Engine
Test and Debug
Deploy
Channels
Publishing
Versioning
Analyze
Introduction
Dashboard Filters
Overview Dashboard
Conversations Dashboard
Users Dashboard
Performance Dashboard
Custom Dashboards
Introduction
Custom Meta Tags
Create Custom Dashboard
Create Custom Dashboard Filters
LLM and Generative AI Logs
NLP Insights
Task Execution Logs
Conversations History
Conversation Flows
Conversation Insights
Feedback Analytics
Usage Metrics
Containment Metrics
Universal Bots
Introduction
Universal Bot Definition
Universal Bot Creation
Training a Universal Bot
Universal Bot Customizations
Enabling Languages
Store
Manage Assistant
Team Collaboration
Plan & Usage
Overview
Usage Plans
Templates
Support Plans
Invoices
Authorization
Conversation Sessions
Multilingual Virtual Assistants
Get Started
Supported Components & Features
Manage Languages
Manage Translation Services
Multiingual Virtual Assistant Behavior
Feedback Survey
Masking PII Details
Variables
Collections
IVR Settings
General Settings
Assistant Management
Manage Namespace
Data
Overview
Data Table
Table Views
App Definitions
Data as Service
HOW TOs
Build a Travel Planning Assistant
Travel Assistant Overview
Create a Travel Virtual Assistant
Design Conversation Skills
Create an ‘Update Booking’ Task
Create a Change Flight Task
Build a Knowledge Graph
Schedule a Smart Alert
Design Digital Skills
Configure Digital Forms
Configure Digital Views
Train the Assistant
Use Traits
Use Patterns
Manage Context Switching
Deploy the Assistant
Use Bot Functions
Use Content Variables
Use Global Variables
Use Web SDK
Build a Banking Assistant
Design Conversation Skills
Create a Sample Banking Assistant
Create a Transfer Funds Task
Create a Update Balance Task
Create a Knowledge Graph
Set Up a Smart Alert
Design Digital Skills
Configure Digital Forms
Configure Digital Views
Add Data to Data Tables
Update Data in Data Tables
Add Data from Digital Forms
Train the Assistant
Composite Entities
Use Traits
Use Patterns for Intents & Entities
Manage Context Switching
Deploy the Assistant
Configure an Agent Transfer
Use Assistant Functions
Use Content Variables
Use Global Variables
Intent Scoping using Group Node
Analyze the Assistant
Create a Custom Dashboard
Use Custom Meta Tags in Filters
Migrate External Bots
Google Dialogflow Bot
APIs & SDKs
API Reference
API Introduction
Rate Limits
API List
koreUtil Libraries
SDK Reference
SDK Introduction
SDK Security
SDK Registration
Web Socket Connect and RTM
Installing the BotKit SDK
Using the BotKit SDK
SDK Events
SDK Functions
SDK Tutorials
BotKit - Blue Prism
BotKit - Flight Search Sample VA
BotKit - Agent Transfer
Widget SDK Tutorial
Web SDK Tutorial
ADMINISTRATION
Introduction to Admin Console
Administration Dashboard
User Management
Add Users
Manage Groups
Manage Roles
Data Tables and Views
Assistant Management
Enrollment
Invite Users
Send Bulk Invites
Import User Data
Synchronize Users from AD
Security & Control
Using Single-Sign On (SSO)
Two-Factor Authentication (2FA)
Security Settings
Cloud Connector
Analytics
Billing
  1. Home
  2. Docs
  3. Virtual Assistants
  4. Test your Bot
  5. Test Case Execution Summary

Test Case Execution Summary

The Test Case Execution Summary allows you to view the test case results, identify the failed test cases, and resolve the flow of the virtual assistant. It gives complete details of the overall test results and the defects found.

The following sections explain the options available on the Conversation Testing to execute the test cases and interpret the results, which help analyze the performance of the test suite as a whole and the individual test cases.

Test Case Execution

You can execute test cases on the Conversation Testing Landing Page and the individual Test Case details page.
Follow these steps for test execution:

  1. On the Test Suite Details page, select the test suite and then click the Run Test Suite button for that specific suite.

    Note: You can also execute the test cases by clicking the Run Test button on the Test Suite Details page.

  2. Choose the Version of the VA you want to test.
    Note: Ensure that you have valid authorization tokens for the VA to make the service calls that would be part of the test suite.

  3. You can monitor the progress of the test suite in the Result column and the status docker. The Result column displays the Passed or Failed status upon successful execution.

When a test case is executed, the test case result is determined with the features like assertions, dynamic texts, OneOf, and so on. To know more, see Test Case Assertion.

The platform simulates all the user inputs against the current VA definition in sequence, as available in the test case. For every user input, the VA’s responses are captured along with the metadata. See Capture Test Suite Metadata under Validate Test Suite to know more.

Test Assertions Execution

The platform performs the assertions tagged to each VA response of a test case. For example, a VA’s response can have Flow, Text, and Context Assertions tagged. The platform performs all three assertions to determine their assertion results.

Flow Assertion

  • For any VA response in a test case, the assertion is determined as pass when the following conditions are true:
    • The Intent ID of the Expected and Actual responses is the same.
    • The Node ID of the Expected and Actual responses is the same.
    • The Transition(s) of the Expected and Actual responses are the same.
    • The Prompt type (Error or User Prompt) is the same in case of Entity nodes.
  • If the above conditions are not met, the assertion is determined as Failed.

Text Assertion

  • For any VA response in a test case, the assertion is determined as passed when the following condition is true:
    • The expected and actual responses are the same (string comparison).
  • Dynamic text values are not considered when performing the comparison.
  • In case of multiple responses in the Expected Output (when a node has multiple variations), one of the expected responses must match for the assertion to pass.

Context Assertion

  • For any VA response in a test case, the context assertion is determined as passed when the following conditions are true:
    • The expected and actual values are the same for the added context variable.
    • A VA response has multiple context assertions and multiple context assertion results.
  • A context assertion fails if the expected value and the actual value of the variable are not the same.
Note: The test case result is determined as Pass only when all the assertions of all the VA responses of the test case are passed.

Past Test Executions

The Past Executions tab is available on the Test Suite summary page, which displays the test result summary of all past executions. The details help in referring to test executions and understanding the results.

Result Summary

The following steps show how to access the test result summary and the details displayed.

    1. Click the Result Summary button to view the summary of all the executions.

  1. Two chat panels are displayed:
  • Ideal Test Suite – It shows Test Cases with metadata and assertions from the test editor.
  • Test Suite Execution – It shows Test results along with the metadata and assertion results identified during Test Execution.

  1. The test result summary is displayed with the following details:
  • Total test cases
  • Breakdown of Passes, Failed, and Not Executed test cases
  • Duration of test case execution
  • The status of the Test Suite – Passed or Failed

    1. The test case details and their assertion result summary are also displayed.

Test Case Execution Summary

The Test Case Execution Summary allows you to view the test case results, identify the failed test cases, and resolve the flow of the virtual assistant. It gives complete details of the overall test results and the defects found.

The following sections explain the options available on the Conversation Testing to execute the test cases and interpret the results, which help analyze the performance of the test suite as a whole and the individual test cases.

Test Case Execution

You can execute test cases on the Conversation Testing Landing Page and the individual Test Case details page.
Follow these steps for test execution:

  1. On the Test Suite Details page, select the test suite and then click the Run Test Suite button for that specific suite.

    Note: You can also execute the test cases by clicking the Run Test button on the Test Suite Details page.

  2. Choose the Version of the VA you want to test.
    Note: Ensure that you have valid authorization tokens for the VA to make the service calls that would be part of the test suite.

  3. You can monitor the progress of the test suite in the Result column and the status docker. The Result column displays the Passed or Failed status upon successful execution.

When a test case is executed, the test case result is determined with the features like assertions, dynamic texts, OneOf, and so on. To know more, see Test Case Assertion.

The platform simulates all the user inputs against the current VA definition in sequence, as available in the test case. For every user input, the VA’s responses are captured along with the metadata. See Capture Test Suite Metadata under Validate Test Suite to know more.

Test Assertions Execution

The platform performs the assertions tagged to each VA response of a test case. For example, a VA’s response can have Flow, Text, and Context Assertions tagged. The platform performs all three assertions to determine their assertion results.

Flow Assertion

  • For any VA response in a test case, the assertion is determined as pass when the following conditions are true:
    • The Intent ID of the Expected and Actual responses is the same.
    • The Node ID of the Expected and Actual responses is the same.
    • The Transition(s) of the Expected and Actual responses are the same.
    • The Prompt type (Error or User Prompt) is the same in case of Entity nodes.
  • If the above conditions are not met, the assertion is determined as Failed.

Text Assertion

  • For any VA response in a test case, the assertion is determined as passed when the following condition is true:
    • The expected and actual responses are the same (string comparison).
  • Dynamic text values are not considered when performing the comparison.
  • In case of multiple responses in the Expected Output (when a node has multiple variations), one of the expected responses must match for the assertion to pass.

Context Assertion

  • For any VA response in a test case, the context assertion is determined as passed when the following conditions are true:
    • The expected and actual values are the same for the added context variable.
    • A VA response has multiple context assertions and multiple context assertion results.
  • A context assertion fails if the expected value and the actual value of the variable are not the same.
Note: The test case result is determined as Pass only when all the assertions of all the VA responses of the test case are passed.

Past Test Executions

The Past Executions tab is available on the Test Suite summary page, which displays the test result summary of all past executions. The details help in referring to test executions and understanding the results.

Result Summary

The following steps show how to access the test result summary and the details displayed.

    1. Click the Result Summary button to view the summary of all the executions.

  1. Two chat panels are displayed:
  • Ideal Test Suite – It shows Test Cases with metadata and assertions from the test editor.
  • Test Suite Execution – It shows Test results along with the metadata and assertion results identified during Test Execution.

  1. The test result summary is displayed with the following details:
  • Total test cases
  • Breakdown of Passes, Failed, and Not Executed test cases
  • Duration of test case execution
  • The status of the Test Suite – Passed or Failed

    1. The test case details and their assertion result summary are also displayed.

Menu