Batch Testing

Once you have built and trained your bot, the most important question that arises is how good is your bot’s learning model? So, evaluating your bot’s performance is important to delineate how good your bot understands the user utterances.

The Batch Testing feature helps you discern the ability of your bot to correctly recognize the expected intents and entities from a given set of utterances. This involves the execution of a series of tests to get a detailed statistical analysis and gauge the performance of your bot’s ML model.

To conduct a batch test, you can use predefined test suites available in the builder or create your own custom test suites. Based on your requirement, the test suites can be run to view the desired results. This option can be accessed from Testing -> Batch Testing option from the left navigation menu.

NOTE: Small Talk testing cannot be automated, you have to use the Utterance Testing option from Testing section for it.

Managing Test Suites

Kore.ai provides a few out-of-the-box Test Suites to perform batch testing. ‘Developer defined utterances’ and ‘Successful user utterances’ are the built-in test suites that can be run to perform Batch Testing. You can also create a New Test Suite for testing a custom set of utterances.

Developer defined utterances

This test suite validates the utterances that have been previously added and trained by the developer from the Machine Learning Utterances screen. Using this test suite would mean testing collectively the entire set of utterances that a developer has added for all tasks of the bot.

Successful user utterances

This test suite includes all the end-user utterances that have successfully matched an intent and the corresponding task is fully executed. You can also find these utterances from the ‘Intent found’ section of the Analyze module.

Adding a New Test Suite

The New Test Suite enables you to import an array of test utterances collectively at once in a batch file, also known as a Dataset. The Dataset file needs to be written in CSV or JSON format and can have a maximum of 1000 (10,000 for on-prem installations) utterances. You can download the sample CSV or JSON file formats as part of the test suite creation using the New Test Suite option.

NOTE: Be aware that the batch suites do not recognize the context values and if present might result in a discrepancy.

JSON Format for Test Suite

JSON format for creating custom suites allows you to define an array of test cases where each test case should consist of an utterance to be tested, the intent against which the utterance to be tested, and optionally define the list of expected entities to be determined from the utterance. If expected intent is a child intent, then you can also include the parent intent to be considered.

• For Entities that have the Multi-Item enabled, values need to be given as: entity1||entity2
• Composite Entities require the values in the following format: component1name:entityValue|component2name:entityValue2
  
• The order in which the entities are to be extracted can be given as: "entityOrder":["TransferAmount", "PayeeName"]. If the order is not provided or partially provided, platform determines the shortest route covering all the entities as the default order.

CSV Format for Test Suite

CSV format for creating custom suites allows you to define test cases as records in CSV file where each test case should consist of an utterance to be tested, the intent against which the utterance to be tested and optionally define entities to be determined from the utterance. If your test case requires more than one entity to detected from a sentence, then you have to include an extra row for each of the additional entities to be detected. If expected intent is a child intent, then you can also include the parent intent to be considered.

• For Entities that have the Multi-Item enabled values need to be given as: entity1||entity2
• Composite Entities require the values in the following format: component1name:entityValue|component2name:entityValue2
• The order of extraction of entity value can be mentioned in the following format: entity3>entity4>entity1. If the order is not provided or partially provided, platform determines the shortest route covering all the entities as the default order.

Entity Format Conversions

Importing a Dataset file

1. Click New Test Suite on the batch testing page. A dialog box to import dataset appears.
2. Enter a Name, Description and choose a Dataset Type in the respective boxes for your dataset file.
3. To import the Dataset file, click Choose File to locate and select a JSON or CSV file containing the utterances as per the Dataset Type selected.
   
   
4. Click Create. The dataset file will appear as an option to run the test suite on the batch testing page:
   

Running Test Suites

The following steps will guide you on how to run a batch test on your bot and obtain a detailed analytical report on the utterances based on the test results. To get started, click Batch Testing in the Testing section on the builder.

To run a Test Suite, for example, the Developer Defined utterances, click Developer Defined Utterances followed by Run Test Suite. This will initiate the batch test for Developer defined utterances.

The test will display the results as explained below. Each test run will create a test report record and displays a summary of the test result. The batch test result in the screenshot below includes the following information:

• Last Run Date that displays the Date and time of the latest test run.
• F1 Score is the weighted average of Precision and Recall.
• Precision is the number of correctly classified utterances divided by the total number of utterances that got classified (correctly or incorrectly) to an existing task ie the ratio of true positives to all classified positives (sum of true and false positives).
• Recall that is the number of correctly classified utterances divided by the total number of utterances that got classified correctly to any existing task or classified incorrectly as an absence of an existing tasks ie the ratio of correctly classified utterances to actual matching intents/tasks (sum of true positives and false negatives).
• Intent Success % that displays the percentage of correct intent recognition that has resulted from the test.
• Entity Success % that displays the percentage of correct entities recognition that has resulted from the test.
• There are three possible outcomes from each test run:
  1. Success – when all records are present in the file are processed
  2. Success with a warning – when one or more records present in the suite are discarded from detection due to system error
  3. Failed – when there were a system error and test could not be resumed post recovery.

  Hovering over the warning/error icon will display a message suggesting the reason.
  

To get a detailed analysis of the test run, click the Download icon to download the test report in CSV format. The top section of the report comprises the summary with the following fields:

• Last Tested: Date of the latest test run for developer-defined utterances.
• Utterance Count: Total number of utterances included in the test run.
• Success/Failure Ratio: Total number of successfully predicted utterances divided by the total count of utterances multiplied by 100.
• True Positive (TP): Percentage of utterances that have correctly matched expected intent.
• True Negative (TN): Percentage of utterances that were not expected to match any intent and they did not match
• False Positive (FP): Percentage of utterances that have matched an unexpected intent.
• False Negative (FN): Percentage of utterances that have not matched expected intent.

The report also provides detailed information on each of the test utterances and the corresponding results.

• Utterances – Utterances used in the corresponding test suite.
• Expected Intent – The intent expected to match for a given utterance
• Matched Intent – The intent that is matched for an utterance during the batch test.
• Parent Intent – The parent intent considered for matching an utterance against an intent.
• Task State – The status of the intent or task against which the intent is identified. Possible values include Configured or Published
• Result Type – Result categorized as True Positive or True Negative or False Positive or False Negative
• Entity Name – The name of the entity detected from the utterance.
• Expected EntityValue – The entity value expected to be determined during the batch test.
• Matched EntityValue – The entity value identified from an utterance.
• Entity Result – Result categorized as True or False to indicate whether the expected entity value is the same as the actual entity value.
• Expected Entity Order – entity values from the input file
• Actual Entity Order –
  • if the order for all expected entities is provided, then the same is included in this column
  • if no order is provided, the system determined order will be included in the column
  • If order is provided for some entities, then a combination of user-defined order and system defined order will be included
• Matched Intent’s Score – For False Positives and False Negatives, the confidence scores from FM, ML and/or KG engines are displayed for the matched intent from the utterance. Note that the scores are given only if the engine detects the intent, that means that you may not see the scores from all the three engines at all times.
• Expected Intent’s Score – For False Positives, the confidence scores for the intent expected to match for the given utterance is given. Again the score will be given by the engines detecting the intent.

Important Notes

• An optimal approach to bot NLP training is to first create a test suite of most of the use cases(user utterances) that the bot needs to identify, run it against the model and start training for the ones that failed.
• Create/update batch testing modules for high usage utterances.
• Publish the trained model only after detailed testing.
• When naming the intent, ensure that the name is relatively short (3-5 words) and does not have special characters or words from the Stop Word list. Try to ensure the intent name is close to what the users request in their utterance.
• Batch Test executions do not consider the context of the user. Hence you might see some False Negatives in the test results which in fact are True Positives in the actual bot when the context is taken into consideration.