Welcome to the Botium Knowledge Center

You can use the Excel file attached to this article as a template:

Botium encourages to use separate worksheets for structuring your content. The naming of the worksheets is important. Without any special configuration, Botium will look for

• Convos in all worksheets with name containing “convo” or “dialog” and not “partial”

• Utterance lists in all worksheets with name containing “utter”

• Partial Convos in all worksheets with name containing “partial”

• Scripting Memory in all worksheets with name containing “scripting” or “memory”

Make sure to meet these conventions in your Excel file.

You can write convos by having two Excel columns as in this example.

!!! attention - Botium will generate the test case names out of the sheet name and the line number where the conversation starts. You can use a 3-column format as well to have your custom test case names (see docs here ).

-   Botium will by default expect **exactly one** header row (otherwise 
your test cases are screwed)

-   Column naming **doesn’t matter**

-   Separate two test convos with **at least one** empty row (otherwise
    your test cases are combined)

-   When starting a test case in the **Bot** column, Botium is actually
    waiting for the chatbot to begin the conversation. This is **not**
    supported by all [Botium Connectors](/technical-reference/botium-connectors/).

You can write utterances lists by having two Excel columns as in this example.

-   Botium will by default expect **exactly one** header row

-   Column naming **doesn’t matter**

-   Start a new utterance lists by adding the reference name in **the
    first column** and use the second column to list the **user
    examples**

In order for the utterances lists to be used by Botium, you have to
enable **utterance exapansion** in the [Scripting
Settings](/faqs/botium-box-usage/what-are-the-scripting-settings-in-botium-box/)!

You can use Botium Scripting in Excel files, using the magic words for utterances, asserters and basically all other BotiumScript structures.

When using multiple asserters on a single response from the Bot, make sure to place all BotiumScript in one cell:

If you are asserting on multiple bot responses, separate them into several cells:

You can as well use the utterance lists defined in an excel file in other file formats:

#me
HELLO_UTT

#bot
Hello, meat bag! How can I help you ?

Use the Dropzone in the Test Sets menu in Botium to quickly upload the Excel file first time to Botium.

A separate test set for further refinement will be created and opened.

When you scroll down on the dashboard you should immediatly see the convos and utterances Botium extracted from the Excel file.

The test set holding your Excel file can now be used as any other test set in Botium:

• Use the Quickstart Wizard to select a chatbot channel, select the test set and let the test cases run against this chatbot. A Test Project will be created automatically to repeat any test session and to CI/CD Integration .

• In the Test Results menu, quickly select a chatbot channel and the test set to run a one-shot test session

When following the steps from above, the Excel file is now linked with Botium, but it cannot be changed from inside Botium - you always have to download and upload it again. To have deeper integration with Botium you can as well import the Excel file content to Botium instead of just linking the Excel file. There are maybe good reasons for it:

• After importing the Excel content, the visual test case designer in Botium can be used

• The Excel content is converted to text-based test cases which can be versioned in a linked Git repository

• When having a test case fail Botium can immediately point you to the troubled test case convo, instead of you having to open the Excel file and look it up there

There is one main downside: As soon as the test cases are imported into Botium, there is no way back. Any changes done to the Excel file won’t be reflected in Botium anymore. From then on the only way to make changes is in Botium.