Get to know Tricentis Tosca

Tricentis Tosca is your one-stop-shop for creating automated tests. You don't have to manually work through your system under test; Tosca does it for you.

For instance:

  • Navigate your system under test: click buttons, open context menus, or work through tool bars.

  • Enter, save, or verify data in web applications, Excel sheets, or databases.

  • Exchange messages with programming interfaces.

  • And much more!

How does Tricentis Tosca know what you want it to do?

To tell Tricentis Tosca what to do and how to do it, you'll use three main elements:

  • Scanning

  • Modules

  • TestCases

What is scanning?

Your system under test has various elements that Tosca needs to interact with. For instance: buttons, text fields, tool bars, cells in tables, SAP dialog windows, etc.

These elements are called controls.

Ultimately, you want Tosca to steer these controls. For instance: click a button, verify data in a table cell, or type text into an entry field.

To make this possible, you need to get the required technical information on these controls into Tricentis Tosca.

This is what scanning your system under test does. When you scan, Tosca performs the following actions:

  • It grabs all required information on the controls that you select.

  • It saves this information as a Module.

For more information on scanning, see chapter "Scan Modules".

What is a Module?

Modules are the building blocks of your tests. They contain the technical information that Tosca needs to navigate and interact with your system under test.

For instance: all available options in a drop-down menu, the headers of an Excel table, or how to select a check box.

In your tests, you use the following Modules:

  • Modules that you create, by scanning your system under test.

  • Modules that Tricentis Tosca provides.

    The Modules of the Standard subset are prepared special tasks that you can adapt to your needs. For instance, the Module OpenUrl is designed to open a URL in a browser window. All you need to do is to specify the URL.

For more information on Modules, see chapter "Create and manage Modules".

Various controls in your system under test Module after scanning

What is a TestCase?

A TestCase is a sequence of actions that you want to perform on your system under test. These actions are called TestSteps. Each TestStep is an automated task that you would otherwise do manually.

To create a TestCase, you perform the following actions:

  • Specify which Modules should make up your TestCase.

    Drag and drop Modules into the order that you need. For instance, you can use the Module OpenUrl from the Standard subset to open a URL. And then use your scanned Module to fill out a form at this address.

    This creates TestSteps from the Modules.

  • Fill out your TestSteps. For instance: enter the text that Tosca should type into a field, select an entry from the drop-down menu, or specify a regular left-click on a button.

For more information on creating TestCases, see chapter "Create and manage TestCases".

Module TestCase with filled-out TestStep that you created from the Module

Create automated tests

Now let's take a look at how to set up automated testing. These are the basic steps you will take in your testing life-cycle:

  1. Identify the requirements that you expect your system under test to fulfill (see chapter "Create and manage Requirements").

  2. Optionally, design a logical test structure to see which tests you need to cover your requirements. Use TestCase-Design to create combinations of possible TestCases (see chapter "Work with TestCase-Design").

  3. Scan your system under test to create Modules (see chapter "Scan Modules").

  4. Create TestCases out of your Modules (see chapter "Create and manage TestCases").

  5. Optionally, create configurations for your tests (see chapter "Configure tests").

    Configurations help you to avoid repetitions and allow you to define environmental information. For instance, you can re-use the same TestCase, but log in with different user credentials each time. Or you can define a default browser for all your tests.

  6. Run your tests (see chapter "Execute tests").

Once you have executed your tests, Tricentis Tosca maps the test results with your requirements. This gives you a good overview of the following:

  • Your testing status.

  • The status of your system under test.

What's next?

Now that you understand the basic functionality of Tricentis Tosca, familiarize yourself with the user interface: