Definition of Terms for the Tosca Commander Objects

In the First Steps tutorial, you will create Modules and a TestCase with TestSteps, then you will run your TestCase.

This chapter explains the basic terms in Tosca and outlines how Tosca TestCases are structured.

TestCases and TestSteps

A TestCase consists of several TestSteps which determine the test process.

TestSteps are processed in sequential order (see chapter "Create TestCases") and each TestStep maps one page of the TricentisSample Application, also known as the test object.


You specify your test data in the TestStepValues of the TestSteps. Tosca uses this test data during test execution, for instance, when a specific text is written to an input field, or when a button is clicked.


Automated TestSteps are based on Modules.

Modules contain technical information which is used to identify and steer screen items. These items can be, for instance, buttons or input fields. Tosca creates a ModuleAttribute for each item and saves this to the Module (see chapter "Create Modules").

In Tosca, test data are separated from technical steering information. This way you can reuse Modules to create various TestSteps for any number of TestCases in order to test a variety of data.


You can create ExecutionLists to run your TestCases and log the results of the test execution (see chapter "Execute TestCases").

Tosca objects

Objects in Tosca Commander





Represent the technical steering information


Determine the test sequence and contain test data


Serve to plan and manage the test execution

Object hierarchy

Objects in Tosca Commander have a strict hierarchical structure. You must keep the object hierarchy when you copy or move objects. This means, for instance, that you cannot copy TestCase folders to TestStep folders or Module folders (see chapter "Drag and drop").

Related chapters