Glossary

The action mode in a test step determines what Tosca Cloud does with that step. For example, to have Tosca Cloud insert something into a text box or check what's in the text box.

Activities are a key component of business flows. They specify what users can do in your application and how these actions connect. Each activity is based on a reusable test step, which defines the actual test actions for an activity.

An agent is a program that runs your test on any machine. This can be a tester's workstation, a virtual machine in your organization's network, or a cloud-based solution hosted in the Tricentis cloud. Administrators set up agents when they set up Tosca Cloud.

A business flow is a best practice solution for using test data in Tosca Cloud. It's a visual representation of all activities that users can perform in your application and how they move through them. Once you have your business flow in place, you can automatically generate test cases from it.

Characteristics determine which agent runs which tests. They function as labels: only agents that have the same characteristics as a playlist can run this particular playlist.

An agent that's hosted in the Tricentis cloud and fully maintained by us. For more information, check out Use cloud agents.

A control is a screen element in your application. For example, a button, text box, menu entry, or table cell. At runtime, Tosca Cloud tries to find the control and interact with it. Check out Supported controls.

A set of test data that you've added to Tosca Cloud.

Elastic Execution Grid is the execution service of Tosca Cloud. It distributes your tests to available agents based on characteristics and collects the test run results.

A module is the result of a scan. It's a representation of a specific part of your application and contains the technical data that Tosca Cloud needs to steer this part of your application at runtime. When you design an automated test case, you use modules to build test sequences and actions.

Third-party identity provider for user management within Tosca Cloud.

Paths are a key component of business flows. They define specific user journeys through all activities in your business flow. You'll use them to automatically generate test cases.

An agent that runs on your local workstation. To have a personal agent on your machine, you need to install local components.

A playlist is a group of test cases that you want to run as a batch.

Reusable test steps are sets of steps that you can reuse across multiple test cases. If anything changes in your application under test and you update your reusable test steps, Tosca Cloud automatically updates all test cases that contain them.

Process of getting all necessary technical information from your application into Tosca Cloud. For details and instructions, check out Scan your application.

A simulation hit happens when the Simulator agent receives an inbound message and processes it, such as performing a verification. The number of simulation hits you can use depends on your Tosca Cloud plan.

Set of pre-built test steps for various useful tasks and actions that Tosca Cloud delivers out-of-the-box.

An agent that's installed on your premises, typically on a virtual machine, and maintained by you. For more information, check out Set up team agents.

A tenant is an instance of Tosca Cloud that is available to a specific group of users. It's the variable part of your Tosca Cloud URL: https://<cloud_organization_name>.my.tricentis.com/. The tenant owns all data and test artifacts of this group of users.

A test case is a sequence of test actions that you want to perform in your application under test. It verifies a specific workflow.

A test run where you run a set of test cases to verify that your test object behaves as expected. Test run results are visible to the whole team.

A test action in your test case. When you design a test case, you use different elements to create automated test actions.

A rehearsal for a test case, to find and fix issues. Trial runs help you make your test cases as stable and reliable as possible before you create a playlist and run them in earnest. Results of trial runs are only visible to the person who triggered it.