Glossary: Tricentis ARA

This chapter describes the most commonly used Tricentis ARA terms.

Term

Description

check out

The check-in/check-out mechanism in multi-user workspaces ensures that users don't interfere with each others work.

Checking out objects locks them to your workspace. Other users can't modify them for as long as they are checked out.

check in

Checking in checked-out objects frees them up for other users.

control

A control is an element in your application that the test can interact with, for instance a button, a text field, or a link (see "Control types").

The test ultimately steers these controls, i.e. interacts with them. For instance, a test can verify text on a webpage, click buttons, or write something into a text box.

Module

Modules are the building blocks of a test. They contain the technical information that an automated TestCase needs to navigate and interact with your application.

Each Module consists of one or more ModuleAttributes.

ModuleAttribute

A ModuleAttribute is a representation of a control that you have selected during the recording.

When you create a TestStep from a Module in Tricentis Tosca, the ModuleAttribute turns into a TestStepValue. You then fill out this TestStepValue to tell the test what to do.

multi-user workspace

A workspace is a database where Tricentis Tosca stores test data.

A multi-user workspace is a database shared between several users. It allows many users to work on the same tests in parallel.

recording

A recording is the sequence of steps to which Tricentis ARA translates your interactions with your application.

steer

Automated tests steer the controls in your application. That means that they interact with the control as a user would. For example, you can design your the test to click a button, choose an element from a drop-down menu, or enter text in a text field.

TestCase

A TestCase is a path taken in your application. It consists of a sequence of steps that you want to test. These steps are called TestSteps. Each TestStep is an automated testing task that you would otherwise do manually.

TestStep

A TestStep is a step in the TestCase, the path that you want the test to perform in your application. A TestStep is an automated testing task that you would otherwise do manually.

TestStepValue

Each TestStep consists of one or more TestStepValues. These are parameters that tell the test exactly what to do.

Tricentis Automation Recording Assistant

Tricentis Automation Recording Assistant is a tool with which you can create TestCases quickly and easily. You can record a TestCase just by using the application as you normally do.

Once you have recorded your TestCases, you can import them to Tricentis Tosca and use them to automate the testing of your application.

Tricentis Tosca

Tricentis Tosca is a powerful tool with which you can automate the testing of your application. It provides all the functionality of Tricentis ARA and much more.

For a comparison of the functionalities of Tricentis ARA and Tricentis Tosca, see "Comparison of Tricentis ARA and Tricentis Tosca".

verify a control

To verify a control means to check whether the control is as expected. For example, you can design your test to verify whether the label on a button is "Confirm", or whether a table cell displays the expected dollar amount.