Glossary
New to Tricentis Test Automation for SAP integrated with SAP Cloud ALM? This glossary explains our most commonly used terms.
action mode |
The Action Mode in a test step determines what Tricentis Test Automation for SAP integrated with SAP Cloud ALM does with that step. For example, should Tricentis Test Automation for SAP integrated with SAP Cloud ALM insert something into a text box or check what's in the text box? |
An agent is a program that runs your test on any machine. |
|
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. |
|
A control is a screen element in your application. For example, a button, text box, menu entry, or table cell. At runtime, Tricentis Test Automation for SAP integrated with SAP Cloud ALM tries to find the control and interact with it. Check out Supported controls. |
|
Elastic Execution Grid is the execution service of Tricentis Test Automation for SAP integrated with SAP Cloud ALM. 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 Tricentis Test Automation for SAP integrated with SAP Cloud ALM 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. |
|
Okta |
Third-party identity provider for user management within Tricentis Test Automation for SAP integrated with SAP Cloud ALM. |
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. |
|
Process of getting all necessary technical information from your application into Tricentis Test Automation for SAP integrated with SAP Cloud ALM. For details and instructions, check out Scan your application. |
|
standard modules |
Set of pre-built test steps for various useful tasks and actions that Tricentis Test Automation for SAP integrated with SAP Cloud ALM 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. |
|
tenant |
A tenant is an instance of Tricentis Test Automation for SAP integrated with SAP Cloud ALM that is available to a specific group of users. It's the variable part of your Tricentis Test Automation for SAP integrated with SAP Cloud ALM URL: https://<cloud_organization_name>.my.tricentis.com/. The tenant owns all data and test artifacts of this group of users. |
test case |
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. |
|
Your work environment in Tricentis Test Automation for SAP integrated with SAP Cloud ALM. All users of a workspace share resources and collaborate. You're either working in the default workspace or a custom workspace that your administrator has created for your organization. |