Welcome to the Botium Knowledge Center

When starting a test session, Botium Box is using a list of asserters:

• The Botium Core Asserters are available everywhere

• Asserters that are selected in the Involved Registered Component(s) field

  

• Asserters that have the Include in Default Component Set switch enabled

All asserters from Botium Core can be used in Botium Box as well.

Botium Box includes asserters typically used in test strategies for chatbots:

• Asserting Hyperlink existance, availability and response in a chatbot response

• Asserting with custom HTTP/JSON API requests

• Asserting SQL Database Content

• and more …

All of these asserters are preconfigured in the Settings / System Settings / Registered Components section.

To enable/disable an asserter:

• Go to Settings / System Settings / Registered Components

• Click the asserter in the list to open the edit view

  • Enable/Disable the Include in Default Component Set switch for having the asserter included in all test sessions by default (enabled) or for having it to select manually (disabled)

  • Enable/Disable the Register as global scripting component switch for making the asserter act for all conversation steps (enabled) or for having it to make part of the script (disabled) - behaviour depends on the asserter implementation

• Don’t forget to click the Save button

Here are generic instructions how to register and configure an asserter in Botium Box.

1. Deploy the Asserter Code (NPM-package, Javascript File) to the Botium Box installation directory

2. Login to botium box with admin rights

3. Goto Global Settings → Components → and click the + NEW button

   

4. Fill out configuration:

   1. Name

   2. Component Type Test Case Asserter

   3. Include in Default Component Set - asserter is available in all test suites by default

   4. Component Ref Code to reference this asserter in your convo files

   5. Component Source is a reference to an NPM package or Javascript-File (has to be available on all Botium Box servers)

      1. Also allowed to use the class name of one of the integrated asserters, for example the Intent Confidence Asserter or the Response Length Asserter

   6. Register as global scripting component to make this asserter be called for all test runs for all convo steps (use with care!)

   7. Component Configuration as JSON-formatted configuration options for the asserter (see asserter documentation)

      

5. Click Save

6. DONE

Now you can use the the asserter in convos by simply add the Component Ref Code.

For a Test Project, you can configure the list of asserters to add in the Involved Registered Components(s) field.

Now you can use the hyper-link-asserter in convos by simply add the Component Ref Code e.g.