Test the Tutorial Bot

This chapter describes step 4 in the RPA Studio First Steps tutorial.

What will you do here? 

You will do a test run of your Tutorial Bot.

For more detailed information on testing Bots, see "Test your Bot".

Why is that important?

Testing your Bot ensures that you have a workable Bot before you publish it. Publishing a Bot moves it over to RPA Orchestrator, where you use it in production.

Video

The following video takes you through the testing process. A step-by-step description is below.

Do a test run

Test runs in RPA Studio are exactly that. RPA Studio does not save results; it only keeps the result of the Bot's latest test run. This result is discarded as soon as one of the following events occurs:

• You change anything about your Bot.

• You test the Bot again.

• You close RPA Studio.

To test your Tutorial Bot, click on the Start icon in the Flowchart tab.

You can also run a Bot by selecting it in the project tree and clicking on Run in the RPA menu, or pressing F6.

After the run has finished, RPA Studio displays the result in the Flowchart tab. The Flowchart shows the result of each Step as well as the actual Bot flow at run-time.

In Results mode, the Details tab turns into the Results tab. The columns in the Results tab contain detailed information on the Bot run (see "Columns in RPA Studio").

If you want to modify your Bot, you need to switch back to Design mode.

To switch back to Design mode, double-click into empty space in the Flowchart tab.

Alternatively, you can click on Design mode in the RPA menu.

What happens if you test the Bot a second time

The Tutorial Bot is designed to run only once.

It takes the Notepad file and saves it as tutorial.txt. So if you test the Bot again, the Save As dialog prompts a different confirmation dialog: This file already exists, do you want to overwrite it? 

The Tutorial Bot does not steer this dialog and, consequently, throws an error.