Cheatography
https://cheatography.com
Concepts, abbreviations and processes for Tricentis' Tosca automated-testing software.
This is a draft cheat sheet. It is a work in progress and is not finished yet.
Abbreviations & Terms
Abbreviation |
Term |
Description |
Example |
SUT |
System Under Test |
The object or target of a measurement test |
Whatever program you want to use Tosca to test. |
TC |
TestCase |
A TestCase is a path taken in your application. It consists of a squence of steps that you want to test. These steps are called TestSteps. |
TCP |
Test Configuration Parameter |
A Test Configuration Parameter is a parameter that you can set for Tosca objects. This way you can configure your tests further |
If a TestCase is to be run on a specific browser, use the TCP to specify which browser Tosca should use to run the test. Use the TCP named "Browser" and set the value to "Firefox", "Chrome", or "Edge" etc |
TDM |
Test Data Management |
External data --> TDM --> Test Object |
Process 1 creates data in the TDM Process 2 uses the data in the TDM Process 2 modifies and updates the data in the TDM Process 3 uses the data in the TDM |
TSF |
TestStepFolder |
|
Precondition
|
TCF |
TestCaseFolder |
A folder containing one or more items, i.e., TestCases, TestStepFolders, TestSteps |
Example 1: One TestCase folder containing 3 TestCases Example 2: One folder containing 3 TestCases; the first TestCase is expanded, so we see that it contains additional TestStep Folders |
|
TestCaseFolder structure |
within a TestCase, use Folders to separate logical sections. Within standard process folders, group TestSteps within a Folder structure |
Precondition > Process > Postcondition |
|
Tosca Objects
Term |
Icon |
Explanation |
Sections |
TestCaseFolder |
|
|
TestCases folder |
TestCase |
|
|
TestCases folder |
Business TestCase |
|
|
TestCases folder |
TestCase Template |
|
|
TestCases folder |
Business TestCase Template |
|
|
TestCases folder |
TestStepFolder |
|
|
TestCases folder |
TestStep |
|
|
TestCases folder |
XTestStep |
|
|
TestCases folder |
Manual TestStep |
|
|
TestCases folder |
TestStepValue |
|
|
TestCases folder |
Manual TestStepValue |
|
|
TestCases folder |
|
Process
Process |
Function/Tool |
Find and select objects for use in TestSteps |
XScan |
Model the SUT |
Modules |
Create Test Scenarios / Processes |
TestCases >> TestSteps |
Context Menu actions (right-click)
Icon |
Function/Tool |
|
Rename |
|
Delete |
|
Search |
|
Open in New Window |
|
Expand All |
|
Collapse All |
|
Checkout |
|
Checkout Tree |
There are more... but they all seem to have HoverText explanations
|
|
Starting off
Step 1 |
Download Tosca Commander |
If you're not an Admin on your machine you will need their help |
Step 2 |
Create your Workspace |
Used for Planning, Creating, and Executing your tests |
Step 3 |
Select Repository type |
Select None if you are working on your own or need to be separate from other testers; anything else would be used for a Common Repository that you'd share with other users' Workspaces. Your Admin should be able to tell you what to select here. |
Step 4 |
Download the Tosca Subset to use as a Template |
This is a .TSU file containing pre-made Tosca artifacts |
Step 5 |
Either include the Template .TSU in the Workspace setup or Import it afterwards |
The Tosca Subsets provide ready-made artifacts that you can use instead of creating them yourself |
|
|
Modules (the key to a Model-based system)
Standard Modules |
Pre-built elements, you don't need to change them |
Upgraded with Tosca |
TBox Automation Tools, TBox xEngines, OSV |
User-created Modules |
Best generated by XScan |
Each element must be unique (green message) |
Elements can be combined into ControlGroups |
|