Tosca Architecture Explained
Tosca Architecture Explained
Introduction
Tosca is a powerful test automation tool developed by Tricentis.
It helps companies automate software testing for faster and reliable results.
Tosca supports testing for web, desktop, APIs, and mobile apps.
To understand how Tosca works, we must learn about its architecture.
Let’s explore the main components of Tosca’s architecture and how they work together.
Key Components of Tosca Architecture
-
Tosca Commander
-
Tosca Workspace
-
Tosca Repository
-
Tosca Execution Engine
-
Distributed Execution (DEX)
-
TestCase Design
-
Modules and TestCases
-
ExecutionLists
-
Integration with Tools
-
Reporting and Analytics
1. Tosca Commander
-
This is the main interface of Tosca.
-
Testers use it to create, manage, and run tests.
-
It is like the control center of Tosca.
-
Everything—TestCases, Modules, Test Data—is handled here.
2. Tosca Workspace
-
A workspace is a user’s own working area.
-
It contains all the test objects needed.
-
Workspaces can be:
-
Private (for individual testers)
-
Shared (for teams)
-
-
Syncing helps teams collaborate on the same project.
3. Tosca Repository
-
A central place where all project data is stored.
-
It uses:
-
Common Repository (for teams)
-
File-based Repository (for individual use)
-
-
It ensures that all test data is safe and accessible.
4. Tosca Execution Engine
-
This is the brain that actually runs the test cases.
-
It reads test steps from the workspace.
-
It controls the browser, desktop, or mobile app under test.
-
It sends results back to Tosca Commander.
5. Distributed Execution (DEX)
-
DEX helps run tests across multiple machines.
-
It uses Agents and Distribution Servers.
-
Helps in parallel testing to save time.
-
Ideal for running tests overnight or in the cloud.
6. TestCase Design
-
Helps create data-driven tests.
-
You can design templates and link test data using combinations.
-
It separates the logic from the data.
-
Easy to maintain and scale.
7. Modules and TestCases
Modules:
-
Modules are reusable components.
-
They contain technical information about UI elements.
-
Created using Tosca’s Scan tool (XScan).
TestCases:
-
Made from Modules.
-
Define what to test and how to test.
-
Can be reused, changed, or updated easily.
8. ExecutionLists
-
Used to organize and run multiple TestCases.
-
You can:
-
Group related tests
-
Schedule test runs
-
Track results in one place
-
-
Helps in running large test sets efficiently.
9. Integration with Tools
Tosca integrates with many tools such as:
-
JIRA – for defect tracking
-
qTest – for test management
-
SAP – for enterprise app testing
-
CI/CD tools like Jenkins and Azure DevOps
-
Git – for version control
This makes Tosca a part of the DevOps and Agile ecosystem.
10. Reporting and Analytics
-
After test execution, Tosca gives detailed reports.
-
You can view:
-
Passed/Failed test steps
-
Execution time
-
Logs and screenshots
-
-
Reports help in debugging and decision making.
Tosca Architecture Flow
Here’s how everything works together:
-
Tester opens Tosca Commander
-
Creates Modules using XScan
-
Builds TestCases using those Modules
-
Stores all data in the Repository
-
Runs tests using ExecutionLists
-
Execution Engine runs tests and captures results
-
Results are shown in Commander or exported to reports
-
Uses DEX for distributed runs, if needed
-
Integrates with tools for defect logging or CI pipelines
Diagram (Text Representation)
Tosca Technologies Used
-
GUT (Generic UI Test) engine for automation
-
TBox – core automation framework
-
XScan – UI object recognition tool
-
Tosca BI – for data warehouse and database testing
-
Tosca API Scan – for API testing
Advantages of Tosca Architecture
-
Modular – Easy to build and maintain tests
-
Scalable – Supports large teams and projects
-
Integrated – Works with Agile and DevOps tools
-
Stable – Reduces flaky tests
-
Reusable – Create once, use many times
Tosca Supports:
-
Web and desktop apps
-
Mobile apps (Android/iOS)
-
APIs (REST/SOAP)
-
SAP and other enterprise tools
-
Databases and BI systems
Real-Life Use Case
A banking company uses Tosca:
-
Business team designs templates in TestCase Design
-
Automation team creates modules with XScan
-
TestCases are built and linked to data
-
Runs daily using DEX across 10 machines
-
Results shared with QA, Dev, and Business teams
Everything works fast, accurate, and error-free.
Conclusion
Tosca’s architecture is designed for powerful, flexible, and scalable test automation.
From designing tests to running them across machines, Tosca covers it all.
Understanding the architecture helps QA teams work faster, smarter, and better.
If you're looking for a modern testing tool with low maintenance and high reuse, Tosca is a great choice.
Comments
Post a Comment