TOSCA Tutorial – Table of Content
The Tosca Tutorial are consists of below articles which are explained the different components of Tosca. While writing the article, we have considered the knowledge of entry level software tester so that they can understand this article easily.
Tosca Tutorial #1: Tosca Overview
Tosca Tutorial #2: Tricentis Tosca Setup – Install, Uninstall and License Configuration
Tosca Tutorial #4: Understanding of TOSCA Commander and Tosca User Management
Tosca Tutorial #5: Tosca Scanning – An Introduction to Modules
Tosca Tutorial #6: Tosca Test Case Creation
Tosca Tutorial #7: Tosca Parameters and Library– Buffer, Business Parameter, TCP
Tosca Tutorial #8:Tosca Test Execution, Reports, and Bug management
Tosca Tutorial #9: Test Case Design – An approach to test data management
Tosca Tutorial #10: Tosca Test Data Management.
Tosca Tutorial #11: API Testing in Tosca
Tosca Tutorial #12: Tosca Interview Questions and Answers
In this Tosca Modules with Tosca Scan article , we will discuss about the Tosca Scan procedure to create Tosca Module with brief descriptions of different terms. Step by step screens are attached for easy understanding of Tosca Scanning approach.
Concepts of Tosca Modules:
Tosca Modules keeps the technical properties of any control that is refer to any test object.
Basically, module creation is the first step to start with test case development in Tosca Commander. Module has to be created for the unit of functional block of the test application. These functional units are, for instance, pages or screens of test websites or any window applications. Any input fields such as buttons, text box, combo list, etc. are known as controls. The controls which are required for test execution, has to be captured in Module as ModuleAttributes.
Tosca modules are classified into below two categories –
· Classic Modules – It is created by classic engines during the scanning.
· XModules – It uses XEngines which are based on the Tosca TBox framework.
The each components of a module are known as ModuleAttributes and the components are known as controls. The Classic Modules have the classic ModuleAttributes, and on the other hand, the XModules have the XModuleAttributes.
Classic Engines: In the early phase of Tosca, Classic Engines are developed to processes the the TestCase information and steers the test object. There is respective engines are available to steer any test object.
TBox: The reference of Tosca Tbox framework algorithm is the basis for XEngines to steer any controls. Same can be applied to steer GUI and non-GUI objects.
XEngines: With the help of XDefinitions, the XEngines are defined in Tosca. The controls for the test objects are hierarchically structured through the XDefinition. So, the tree structure of the test objects are mapped with controls of any modules.
The Tosca TBox is compatible with the below engines:-
· Tosca XScan 3.0 – After scanning the test objects (GUI or Non GUI), each time Tosca creates Modules which contains the technical properties. This technical properties are required to steer any test objects as controls. Scanning can be done from Modules sections only. So, modules are saved in “Module” section. We can scan any application by Right-clicking onto a Module folder and select the technology of the application such as, desktop, mobile, html, SAP, etc.
· Tosca AnyUI Engine 3.0 – It allows applications with user interfaces to be steered, independent of the underlying technology.
· Tosca API Engine 3.0 –API Engine creates modules for application programming interfaces which is accessed through web service media.
· Tosca Database Engine 3.0 – It allows to work with databases as a part of database automation.
· Tosca DotNet Engine 3.0 – It allows WinForms applications to be tested that were built with Microsoft dotNET Framework 4.6.
· Tosca Java Swing Engine 3.0 – It is used to scan the Java Swing applications for test automation.
· Tosca JavaFX Engine 3.0 – It is used to scan the JavaFX applications for test automation
· Tosca Java SWT Engine 3.0 – It is used to scan the Java SWT applications for test automation
· Tosca Mobile+ Engine – It allows different types of mobile applications (e.g. web, native, hybrid apps) to be steered on both smartphones and tablets. For older version of android/ios, these engines are used for scanning.
· Tosca Mobile Engine 3.0 – It is used to test mobile apps on both smartphones and tablets.
· Tosca SAP Engine 3.0 – It is used to scan and test the SAP applications.
· Tosca Webservice Engine 3.0 – Tosca Webservice Engine 3.0 allows Webservices to be steered via Hypertext Transfer Protocol (HTTP). Webservices using SOAP (Simple Object Acces Protocol) or REST Webservices (Representational State Transfer) can be steered.
· Tosca XML Engine 3.0 – It is used to interact with XML data to change, create or verify the data.
What is the Standard Module?
With the workspace creation, Tosca provides few modules which are used to perform very common operations such that open file, invoke application, string operations, buffer operations, close application, verifications, etc. These modules are known as standard modules. The most important standard modules are –
TBox Automation Tools:
· Basic Windows Operations
· Buffer Operations
· Expression Evaluation
· File Operations
· Folder Operations
· Numeric Operations
· Process Operations
· Resource Handling
· Parameter Data
· File, XML, JSON
· SAP, Java
Test Data Service:
· TestData – Find & provide record
· TestData – Create & provide new record
· TestData – Update Record
· TestData – Move record to TDS type
· TestData – Delete Record
· TestData – Update type
· TestData – Expert Module
Scanning through Tosca is an approach to create Tosca modules which contain all the technical information for any test application.
Step-by-step guide of Tosca Scan to create a module:
We can initiate Tosca scan either right-clicking on Module folder or selecting the dynamic menu Modules and click on Scan icon. In this application, we will learn the scanning with a sample web application.
Tosca Scan – Classic Modules:
Tosca wizard is a part Tricentis Tosca and used for classic scanning to create classic modules. Generally, for legacy applications which are not properly compatible for TBox Scan, we are using this approach of scanning. We can open the Tosca wizard as a standalone application from Start Menu or by selecting the option “Scan More->Legacy Scan” during scanning. Please click here to read more on this topic.
- Main Navigation Panel – Shows the scanned controls.
- Automation Property – Mandatary technical information about the selected controls.
- Scan – Start scanning of the entire region.
- Scan Region – Scan selected region.
- Create Module – Save to create a module for the scanned region. Classic modules are looking like below image –
Tosca Scan – Tbox Module:
Tosca XScan is a part Tricentis Tosca and used for TBox scanning to create Tbox modules. During the scanning, we need to select the engines based on the test application. Scanning steps –
Step# 1: Go to Modules section and select scan path “ScanàApplication”.
Step# 2: Select the test application from “Application Selection” screen and click on Scan button.
Step#3: Xscan screen will be displayed. Here all the available controls are shown here along with technical properties of each of the controls. Based on the properties selected, the control is getting identified by Tosca. There are four different ways to identify the controls –
Identify by Properties – Here based on the technical properties of the test object, controls are getting identified. Always we should prefer technical properties like name, id, class, test, inner text to recognize the controls in the application.
If the properties are not enough to identify any particular controls, we should go for other “Identified by” options which are available in Tbox Scan.
Identify by Anchor – In this method, we need to identify the test object with the reference of any other object which was identified uniquely. It uses algorithm Shortest Path or Coordinate for referenced controls. Here, we need to follow the options after clicking on “Select on Screen” button.
Identify by Image – Based on the image view of the test object. We can allow Tosca to recognize the control. But this is not a preferred method, and it should have opted at the last when all other options are not able to recognize the test objects.
Identify by Index – Index is basically the number of occurrence of the test object. It’s denoted by numeric value, starting with 1.
We can highlight the selected controls using the “Highlight selection” option. Also, we can directly select a control from the application itself by choosing the option “Select on Screen”. Once the object identifies uniquely, we need to click Save or Finish Screen icon (available in the left top) to create a module.
Step# 4: Click on “Finish Screen” to clear the current scanned information. After this, click on Start Screen option to start afresh scanning of a new page. TBox modules will look like below –
In this article of Tricentis Tosca Tutorial, we have covered about Tosca Workspace Creation so that we can start with working with Tosca Commander. Need more information, please click here to visit Tricentis Support portal.