Tosca Distributed Execution SetUp

Distributed Execution with Automation Object Service(withAOS):

1. Create tests

Tosca Distributed Execution is available for multi-user environments. This means that you and other users share a common repository, which is a database that stores test data and test results. Each user retrieves test data, modifies the data, and checks in their changes to the same repository.

You create your tests in Tosca Commander. To do so, you need a workspace that has access to the common repository. Each instance of Tosca Commander on which you want to create tests and trigger executions requires a separate workspace.

2. Trigger execution

When you trigger the execution of a TestEvent in Tosca Commander, it sends the request to the Tosca Distribution Server.

3. Retrieve test data

The server retrieves the test data from the common repository through the Automation Object Service. This service accesses the common repository through a workspace.

4. Distribute execution tasks

The TestEvent whose execution you triggered contains several ExecutionLists. The Tosca Distribution Server distributes these ExecutionLists between the available Tosca Distribution Agents.

Agents synchronize with the server on a regular basis. Once an agent contacts the server, the server hands over the first ExecutionList of the TestEvent to this agent. As soon as the next agent contacts the server, the server hands over the second ExecutionList of the TestEvent to this agent. If there are no agents available, the server queues the ExecutionList(s) until an agent becomes available.

5-6. Save test results

Once a Tosca Distribution Agent has executed an ExecutionList, it sends the results to the server which in turn saves the results to the common repository through the Automation Object Service.

You can monitor the execution of your tests and view the test results with the Distributed Execution Monitor.

Distributed Execution Monitor - The Distributed Execution Monitor is a web-based application that is part of the Tricentis Tosca Server installation.

With the Distributed Execution Monitor, you can do the following:

1. configure your agents
2. monitor and recover your agents
3. monitor the execution of TestEvents
4. cancel the execution of TestEvents

Tricentis recommends installing the Distributed Execution Monitor and the Tosca Distribution Server on the same machine.

Distributed Execution without Automation Object Service(withoutAOS)-

Distributed Execution without AOS works similarly up until the point where the Tosca Distribution Server receives the request to execute from Tosca Commander.

1. Create tests

Tosca Distributed Execution is available for multi-user environments. This means that you and other users share a common repository, which is a database that stores test data and test results. Each user retrieves test data, modifies the data, and checks in their changes to the same repository.

You create your tests in Tosca Commander. To do so, you need a workspace that has access to the common repository. Each instance of Tosca Commander on which you want to create tests and trigger executions requires a separate workspace.

2. Trigger execution

When you trigger the execution of a TestEvent in Tosca Commander, it sends the request to the Tosca Distribution Server.

3. Distribute execution tasks

The TestEvent whose execution you triggered contains several ExecutionLists. The Tosca Distribution Server distributes these ExecutionLists between the available Tosca Distribution Agents.

Agents synchronize with the server on a regular basis. Once an agent contacts the server, the server hands over the first ExecutionList of the TestEvent to this agent. As soon as the next agent contacts the server, the server hands over the second ExecutionList of the TestEvent to this agent. If there are no agents available, the server queues the ExecutionList(s) until an agent becomes available.

4. Retrieve test data

As the Tosca Distribution Server cannot access the common repository, it cannot retrieve test data. It only distributes the request to available agents. Consequently, each agent retrieves the test data from the repository directly.

5. Save test results

Once an agent has executed an ExecutionList, it saves the test results to the common repository.

To retrieve test data and save test results, each agent needs a separate workspace which has access to the common repository.

You can monitor the execution of your tests and view the test results with the Distributed Execution Monitor.

Advantages of Distributed Execution with Automation Object Service(withAOS) - 

Faster setup

Distributed Execution with AOS is easier to configure. You don't need to set up a workspace for every Tosca Distribution Agent.

Performance gain

Distributed Execution with AOS is more efficient. Tosca Distribution Agents work independently from a central repository and don't need to query a workspace for items to execute.

Better handling of multiple common repositories

Unlike Distributed Execution without AOS, agents in Distributed Execution with AOS don't have their own workspaces. The Automation Object Service is the single point of contact to the common repository, and you can set it up to work with multiple common repositories. When you switch to work on a new common repository in Tosca Commander, you do not need to switch anything manually.

Can run the same ExecutionList in parallel

In Distributed Execution without AOS, an ExecutionList can only run on one agent at any given time. So if the same ExecutionList is part of several TestEvents, then it is possible that the execution of some TestEvents cannot progress until that ExecutionList runs as part of another TestEvent.

In Distributed Execution with AOS, the same ExecutionList can run in parallel on several agents. This results in significant performance improvements.

Can specify a test results folder for each TestEvent

In Distributed Execution without AOS, you can define multiple test results folders and save the test results of each TestEvent to a different folder.

Note - Tricentis recommends using Distributed Execution with AOS. 

Distributed Execution with AOS has a number of advantages over Distributed Execution without AOS.

What are the components of TBox?

Tosca XScan:

To assist you in identifying controls in your test application, Tosca XScan provides various identification options. Tosca XScan identifies controls based on their attributes, the default identification method. If controls cannot be uniquely identified by their controls, there are additional ways to identify them.

Controls can be identified in the following ways:

• Identify controls by properties,
• Identify controls via anchor,
• Identify controls by index,
• and Identify controls via an image.

Tosca XML Engine:

Tosca XML Engine 3.0 allows you to modify, create, validate, and verify XML structures. XML elements, CDATA sections, and XML declarations can all have their properties, values, and comments guided at the same time. The Tosca XML Engine 3.0 is included in the basic installation of Tricentis Tosca.

Tosca XBrowser Engine:

Tosca XScan allows you to construct XBrowser Modules for web application testing. You'll need to install the Tosca Automation Extension for your browser to use the XBrowser Engine. Depending on your browser, you can install it immediately or manually.

Tosca Webservice Engine:

Tosca Webservice Engine 3.0 allows you to steer Web Services using HTTP (HTTP). It's possible to guide web services that use SOAP (Simple Object Access Protocol) or REST Webservices (Representational State Transfer). During the basic Tricentis Tosca installation, the Tosca Webservice Engine 3.0 is deployed automatically.

Tosca Mobile Engine:

Tosca Mobile Engine 3.0 from Tricentis allows you to automate the testing of mobile applications. TestCases can be run on various mobile platforms, devices, and applications utilizing various connection methods. The topics in this chapter cover how to set up and run tests with the Mobile Engine 3.0.

How many types of Engines available in Tosca

Tosca has two types of engines – 

1. Classic (or version 1.0) engines 

2. TBox (or version 3.0) engines

Tricentis’ TBox engine was introduced in the 7.x series and has several advantages. Tricentis has been creating more and more TBox engine modules.

Tosca has discontinuing support for Tosca’s classic engines after the planned release of Tosca 15.1 in February 2022. 

Please Check out  blog for more information: http://ow.ly/UOM750HFOeK

Types of Modules in Tosca

Tosca has two types  of Modules:

Classic Modules - Use classic engines to steer test objects.
XModules - Use XEngines which are based on the Tosca TBox Framework.

What is Index, Notations or ResultCount in Tosca

What is Self-Healing Mode in Tosca

What is Cardinality in Tosca

What are all the Standard Modules available for TDS in Tosca.

What are all the Standard Modules available for TDS in Tosca.

1. TestData - Find&provide item
2. TestData - Create & provide new item
3. TestData - Update item
4. TestData - Move item to type
5. TestData - Delete item
6. TestData - Import items
7. TestData - Export items
8. TestData - Update type
9. TestData - Expert module

What are all the Standard Modules available for EXCEL in Tosca.

What are all the Standard Modules available for EXCEL in Tosca.

1. TBox Open Excel Workbook
2. TBox Close Excel Workbook
3. TBox Define Excel Range
4. TBox Create Excel Worksheet
5. TBox Excel Range Manipulation
6. TBox Run Excel Macro
7. TBox Delete Excel Worksheet
8. TBox Update Excel Worksheet
9. TBox Clear Excel Range
10. TBox Excel 1:1 File Compare

What are all the Standard Modules available for SAP in Tosca.

What are all the Standard Modules available for SAP in Tosca.

SAP ContextMenu

SAL Login

SAP Logon

SAP Menu

SAP Multiple Logon Licence Warning

SAP Statusbar

SAP SubToolBar

SAP Toolbar

SAP TreeView

SAP Logon-               Open with Solution Manager

SAP Emulated Tree

SAP Emulated Table Tree

Classes::

  ContextMenuEntry

  MenuEntry

  TreeMenuEntry

What are all the Standard Modules available for Folder Operations in Tosca.

What are all the Standard Modules available for Folder Operations in Tosca.

1. TBox Create Folder
2. TBox Delete Folder
3. TBox Copy Folder
4. TBox Folder Existence

What are all the Standard Modules available for File Operations in Tosca.

What are all the Standard Modules available for File Operations in Tosca.

1. TBox Image Compare
2. TBox File Existence
3. TBox File Compare
4. TBox Delete File
5. TBox Copy File
6. TBox Read/Create File
7. TBox Append File
8. TBox Move/Rename File

What are all the Standard Modules available for Buffer Operations in Tosca.

What are all the Standard Modules available for Buffer Operations in Tosca.

1. TBox Name To Buffer
2. TBox Delete Buffer
3. TBox Set Buffer
4. TBox Partial Buffer

What are all the Standard Modules available for Windows Operations in Tosca Standard Modules.

What are all the Standard Modules available for Windows Operations in Tosca Standard Modules.

1. TBox Take Screenshot
2. TBox Clipbord
3. TBox Send Keys
4. TBox Window Operation
5. TBox Scroll Window Operation
6. TBox Save As
7. TBox Dialog
8. TBox Context Menu

TQL

 Tosca Query language (TQL) is one of the most underrated but powerful query language.

The TQL search is context-dependent. This means that the starting point has an effect on the search to be carried out. A search, which is performed on the basis of a project root element, produces different results from one based on the topmost Module folder.

TQL is deeply rooted in Tosca. Even the normal, Simple Search dialog is based on it.

Q.  How we would like to know if all created TestCases have been assigned to ExecutionLists.

=>SUBPARTS:TestCase[COUNT("ExecutionEntries")==0]

Q. Below query can be used to identify modules which are not linked to any test steps. This can be more useful to identify ideal module and further those can be used or deleted.

=>SUBPARTS:XModule[COUNT("TestSteps")==0]
OR
->COMPLEMENT(=>SUBPARTS:XModule,=>return SUBPARTS:XModule->TestSteps)

Q. Below query can be used to identify test cases which are not linked to any execution list and which are 3 years old. this can be used to identify scripts which are likely to be deleted due to less usages.

->INTERSECTION(->COMPLEMENT(=>SUBPARTS:TestCase,=>return SUBPARTS:TestCase->ExecutionEntries),=>SUBPARTS:TestCase[CreatedAt <= "6/29/2020 2:14:36 AM"])

Q. Below query can be used to identify test cases that don’t have reusable Test block. as per best practice your test script must have good amount of RTBS for quick maintenance (there can be few exceptions).

->COMPLEMENT(=>SUBPARTS:TestCase,=>SUBPARTS:TestStepFolderReference->TestCase))

Q. Below query can be used to identify duplicate modules (specially standard modules) with same name. this further can be used to cleanup duplicate modules.

=>SUBPARTS:XModule[Name == "OpenUrl"]

Q. Below query can be used to identify requirements that are having zero weightage.

=>SUBPARTS:Requirement[Weight==0]

What is the difference between TestCase Design and the Test Data Service ?

TCD - Test Case Design can be thought of as a design mechanism, which structures TestCases strategically to include all the variants and pathways for the SUT. Some static data values can be added, but this data is non-consumable, that is it can be used multiple times and simultaneously. 

Note - TestCase Design Stractures TestCases Startegically to include all different variants for the SUT. 

Some static and non-consumable data.

TDS - Test Data Service, acts as a data repository, where data can be stored, retrieved and updated and its status easily viewed by multiple people. Furthermore, TDS stores consumable or dynamic data that regularly changes. This data can generally only be used once and by one machine at a time.

Note- TestData Service acts as a data repository. 

Consumable and dynamic data. 

Control Types in Tosca

1. Button 
2. CheckBox
3. Control Groups
4. GenericGUI
5. Image
6. Label
7. Link
8. ListBox
9. Menu
10. Radio Button
11. Slider
12. TabControl
13. Table
14. TableTreee
15. TextBox
16. TreeView
17. Window

Tosca Frameworks

Tosca frameworks :  Tosca has two different automation frameworks for recognizing controls and creating modules.

1. TBox.

2. Classic Framework. 

The Tosca TBox framework is used to power UI and non-UI programs like XBrowser, GUI, API, XML, and others. It was written in C#.  All other apps that aren't supported by the TBox framework are built using the classic framework. Windows 32, Excel, and other programs are among them. The visual Basic script is used to create the traditional engine.

TBox Framework - 

The Tosca TBox framework is the basis for steering all engines 3.0, for both Graphical User Interface (GUI) tests and non-GUI tests. It is built on .NET technology and provides you with additional testing functionalities, such as Business Recovery or XBrowser.

The Tbox framework offers the following advantages over Classic Engines:

• Higher performance in the creation and execution of tests.
• One common interface for all supported technologies
• Easy creation of XModules and TestCases with XScan and Tosca Recorder.
• Common dynamic expressions that behave the same way for all Engines 3.0
• A broader range of ActionModes.
• It is Part of Standard Tosca Installation 
• Common interface fpr all technologies.

Classic Framework - 

1. AUTs not recognized by TBox are scanned.

2. Built on VBScript.

3. Comparatively Low Performance.

4. Aid Packs are available for additional set of Modules.

What is the difference between reusable component and module ?

In TOSCA, a reusable component is a predefined set of actions or functionality that can be reused across test cases. A module,  on the other hand, is a collection of actions or test steps that can be used within a test case, making it a part of the test case. 

What are some strategies for using TOSCA to perform regression testing ?

Strategies for regression testing in TOSCA include reusing existing test cases, automating repetitive tests and executing a subset of test cases focused on areas impacted by recent changes. Additionally, creating a regression test suite can help streamline the process.

How does TOSCA handle Integration Testing ?

TOSCA supports integration testing by allowing the creation of test cases that validate interactions between different components or services within an application. These test cases can ensure that the integrated components work correctly as whole.

What are some techniques for optimizing TOSCA test suite Execution performance ?

Optimizing TOSCA test suite execution can be achieved through techniques like parallel test execution, selective test case execution, using test data efficiently and minimizing unnecessary waiting times in test scripts.

How does TOSCA facilitate Portability and Interoperability across Cloud platforms. ?

TOSCA promotes portability and interoperability by using standardized templates and descriptions of cloud applications and services. These templates are platform agnostic, enabling seamless deployment and management across different cloud platform that support TOSCA specifications. 

Explain the Concept of TOSCA's risk-based testing ?

TOSCA's risk-based testing is an approach where test cases and scenarios are prioritized based on the preceived risks associated with different parts of the application. It allows testers to focus more on critical areas and functionalities, ensuring comprehensive testing while optimizing resource allocation.

What are the different types of TOSCA artifacts ?

TOSCA artifacts include Service Templates, Node Templates, Policy Templates, Artifact Templates, Node Types and Relationship Types among others. These artifacts are used to define and model various aspects of cloud applications and services within the TOSCA framework.

How Can you handle data-driven testing for mobile apps in TOSCA ?

Data-driven testing in TOSCA involves parameterizing  test steps and binding them to external data sources, such as spreadsheets or databases. TOSCA allows you to specify test data variations and iterate through different data sets during test executions.

Which type of testing are commonly used with TOSCA

TOSCA supports various types of testing, including Functional testing, Regression testing, Load testing, Security testing , Mobile testing and  Data-driven testing among others.

What is TCshell ?

TCshell is the command-line interface provided by TOSCA. It allows you to perform various tasks, such as executing tests, managing test data and interacting with TOSCA's functionality through command-line commands

Describes the steps involved in creating a mobile test case using TOSCA.

To create a mobile test case in TOSCA, you typically follow these steps.

1. Define the test objectives and scope.
2. Set up a mobile device configurations
3. Create a mobile test module in Tosca Commander
4. Add test steps for interacting with the mobile app.
5. Parameterize and data bind test steps
6. Configure device synchronization settings
7. Execute and validate the mobile test case.

How to take screenshots in TOSCA ?

1. TBox Screenshot Module
2. Dokusnapper.

Shortcut keys for Expand All and Collapse All ?

 

Ctrl + +  ---- Expand All

Ctrl + -   ---- Collapse All

Loop Statements in tosca

There are 2 types of loops available in TOSCA. 

1. Increment Loops - Used for execution in set number of times.

2. Dynamic Loops - Used when loop will be executed until a condition is met. 

• If Statement
• Do statement
• While statement

NOTE: 

If

Condition(within the IF statement)

THEN (Withing the IF statement)

ELSE (Optional)

Do 

Loop (within the DO statement)

Condition (within the DO statement)

While

Condition (within the WHILE statement)

Loop (Within the WHILE statement)

What is Business Parameters ?

Business Parameters Allow your modify values in reusable test step blocks reference without changing the blocks in library.

Business relevant elements of your TC whose values you want to steer to your TC.

Create in library and drag drop in values section to refer them. 

What is Buffer in TOSCA ?

Buffer term in TOSCA is used to refer to the values which can be saved in TOSCA commander and reused in TOSCA.

If input values are needed more than once, they can be buffered using the Action mode Buffer. 

Values or control properties can be saved to a global vailable buffer and read out at any point of the test execution.

What does Constraint Action Mode do ?

Constraint action mode that allows to identify one specific item in a list of similar items. 

It should be uniquely identifiable. 

Note - In the table search, If more than one element found, you can  also limit the number of results to only one element by entering  #<n> in the superordinate node. 

What is Select Action Mode used For ?

Passive action mode used for navigationg tables or drop down menus but without engaging with the app .

The Action mode Select allows you to select specified nodes. The required node must have a unique. 

What are different Action Modes in TOSCA ?

1. Input
2. Insert
3. Verify
4. Buffer
5. Wait On
6. Select
7. Constraint

What is TCP ?

Test Configuration Parameter which can be set for TOSCA objects.

TCP Examples - Browsers, Test Object Version, Test Env Identifier etc.

Advantages - Simply maintenance and avoid repetition.

TCP can be set at Test Case Folder, Test Cases, Execution list etc. 

NOTE : Same TCP on Test Case Folder, Test Case Step And Execution List. 

TCP on execution list will override it.

What diifferent data types exist in TOSCA ?

1. String
2. Date
3. Numeric
4. Boolean
5. Password

How to add Module to a test Step ?

1. Drag and Drop the module.
2. Right click on Test Case >> Search and Add Test Step (Ctrl+T)

What different work states exists in TOSCA ?

1. Planned
2. In Work
3. Completed

What is Test Creation Short cut ?

Ctrl+N 

Ctrl+T

What Object Identification method exists in TOSCA ?

1. Identify by Properties
2. Identify by Anchor
3. Identify by Parent
4. Identify by Image
5. Identify by Index

What is Execution list ?

1. Execute Test Cases and store it.
2. Repetition can be used in Execution list to run as many times.
3. Section of Test Case can also be imported.
4. Execution Command : F6 / Right Click and Click Run.

Different types of Error in TOSCA

1. Verification Failure  :: Expected  output not matching actual output.
2. User Abort :: User abouts the execution.
3. Dialog Failure :: Interaction between TOSCA and AUT fails. AUT is not steerable as the object/property does not exist or not matching. 
4. Test configuration errors: These occur if the test environment isn't set up correctly.
5. Execution errors: These occur when test cases fail during execution.
6. Syntax errors: These occur when there's a mistake in the test data or a keyword is used incorrectly.
7. System errors: These occur when there's a system failure or issue.

Benefits of using Tosca as a test automation tool. ?

1. Script less automation
2. Automation of both UI and Non UI applications
3. Provides end to end automation testing features in one tool.
4. Dedicated customer support
5. Integration with Tricentis products as well as commonly used third party applications like HP-ALM and JIRA.
6. Provides in built modules for frequently used automation functions.
7. Provides support for common technologies like SAP, Oracle, HTML etc.
8. Easy object identification features.
9. Reasonable cost and GUI.
10. Requirement Traceability and Risk based testing approach.

List out the main Components of TOSCA Test Suite.

1. Tosca Commander
2. Tosca Executor
3. Tosca XScan(Tosca Wizard)
4. Test Repository/ Common Repository.

Features of TOSCA

1. Model based test automation.
2. Drag and drop feature allows script less automation.
3. Risk based testing
4. Faster execution and continuous testing available to support DEVOPS.
5. Maintenance effort is minimal
6. Dedicated Support
7. Possible to automation both UI and Non UI.
8. Exploratory Testing available in which user can record their activity and convert into test cases.
9. Distributed Execution.
10. Test Data Management.

Explain the types of Excel modules in TOSCA?

There are several Automation Modules which are part of the standard subset which can be used to automate all the tasks related to Excel Workbook.

Some of the Tosca Automation Modules are listed below:

1. TBox Open Excel Workbook - Used to open or create an Excel file
2. TBox Define Excel Range - Used to define a data range in Excel sheet which we want to steer
3. TBox Create Excel Worksheet - Used to create a new worksheet
4. TBox Delete Excel Worksheet - Used to delete an existing worksheet
5. TBox Update Excel Worksheet - Used to update an existing worksheet
6. TBox Excel Range Manipulation - Used to manipulate data in an Excel file
7. TBox Clear Excel Range - Used to clear data and formatting from a range of cells
8. TBox Run Excel Macro - Used to run existing Excel macros
9. TBox Close Excel Workbook - Used to close an open workbook and save it
10. TBox Excel 1:1 File Compare - Used to compare the cell contents, cell formatting, and objects of two Excel files

Software Bug Life Cycle

 

🌱 New: The journey begins with the discovery of a new defect during testing. These bugs undergo confirmation and testing as new features are uncovered.

🔖 Assigned: Approved bugs are assigned to the development team for resolution, transitioning the status from New to Assigned.

🚪 Open: Developers initiate analysis and potential bug fixes. If deemed insufficient or requiring further scrutiny, the bug may be moved to subsequent stages like Reject or Not.

🔁 Duplicate: When developers identify defects similar to existing ones, or if they coincide with others, the status is marked as Duplicate.

✅ Fixed: Upon completion of debugging tasks and necessary changes, the defect status is marked as Fixed.

🔍 Pending Retest: Post-fixing, developers provide testers with a defect check. The status remains pending until testers verify the fix.

🔬 Retest: Testers review the defect to ensure it's been appropriately corrected.

🔄 Reopened: If issues persist, developers must recheck and reopen the defect status.

✔️ Verified: If testers encounter no issues after developer-provided testing and believe it's properly addressed, the status becomes Verified or Confirmed.

🔒 Closed: With no lingering issues, testers close the defect status.