Tricentis Tosca Tutorial: Getting Started With Model-Based Testing
Tricentis Tosca is an enterprise test automation platform built around model-based testing — an approach where tests are defined at the business layer rather than the technical layer. Instead of writing code that clicks buttons and fills fields, you define modules that represent UI components and business actions, then compose tests from those modules.
This tutorial covers the core Tosca concepts and how to build your first automated test from scratch.
What Makes Tosca Different
Most test automation tools require you to write code. Selenium tests are Java or Python. Playwright tests are JavaScript. Tosca takes a different approach: tests are composed visually from pre-built modules in a workspace, with no programming required.
The tradeoff is architecture overhead up front. In Selenium, you can write a test in an hour. In Tosca, you spend time building the module library first, then compose tests quickly from that library. The investment pays off at scale — with a solid module library, business analysts can write new test cases without engineering involvement.
Tosca targets large enterprises where test maintenance cost at scale outweighs the setup cost of the model-based approach.
Core Tosca Concepts
Modules: A module represents a UI component — a login form, a search bar, a product card. It contains the technical details for interacting with that component (selectors, XPath expressions, API endpoints). You build modules once, reuse them everywhere.
Test Cases: Composed from modules. A "User Login" test case strings together modules: Navigate to Login, Enter Credentials, Submit Form, Verify Dashboard. Test cases contain no technical details — just business actions.
Test Configuration: Defines where tests run — which browser, which environment, which test data. A test configuration maps to a specific execution context.
TestSheets: Organize test cases into logical groups. A TestSheet might contain all tests for the checkout flow.
Execution Lists: Define which tests run as part of a test suite. Create execution lists for regression testing, smoke testing, or sprint-specific testing.
Installing Tosca
Tosca is a Windows-based desktop application. Requirements:
- Windows 10 or Windows Server 2019+
- 8 GB RAM minimum (16 GB recommended)
- Tricentis license (contact sales for trial)
- For web testing: Chrome, Firefox, or Edge
Download from the Tricentis Customer Portal after license activation. Install includes Tosca Commander (the main UI), Tosca CI (for command-line execution), and the Tosca Server components.
Creating Your First Module
Start by scanning the UI component you want to automate. Tosca's TBox scanning technology identifies UI elements and generates module attributes automatically.
Step 1: Create a Project In Tosca Commander, navigate to Modules > right-click > Create Module Folder. Name it LoginPage.
Step 2: Scan the Login Page
- Open Chrome to your application's login page
- In Tosca Commander, go to Modules and click the scan icon (or use Ctrl+Shift+A)
- Tosca opens its overlay tool
- Click each element you want to include: email field, password field, submit button, error message area
- Each click generates a module attribute with the technical details (selector, XPath, position)
Step 3: Define Module Actions For each attribute, set the action:
- Email field → Action:
InputText - Password field → Action:
InputText - Submit button → Action:
Click - Error message → Action:
Verify
Step 4: Parameterize the Module Replace hardcoded values with parameters:
- Email value:
{EP}EmailAddress(EP = Equivalence Partition) - Password value:
{EP}Password
Parameters allow the same module to be used with different test data.
Creating a Test Case
With the login module built, create a test case:
- Navigate to TestCases in the workspace
- Right-click > Create TestCase, name it
User Login - Valid Credentials - Drag the Login Page module into the test case
- Drag the Dashboard module (create this similarly) for the post-login verification
- In the test case, set parameter values:
- EmailAddress:
test@example.com - Password:
TestPass123!
- EmailAddress:
The test case looks like:
[TestCase] User Login - Valid Credentials
[Module] Navigate to Login Page
URL: https://app.example.com/login
[Module] Login Form
EmailAddress: test@example.com
Password: TestPass123!
Action: Submit
[Module] Dashboard Verification
WelcomeMessage: Verify = "Welcome, Test User"No code. Business-readable test definition.
Test Data Management
Tosca's TestDataService (TDS) manages test data separately from test logic:
- Create a TDS workspace file with columns matching your module parameters
- Link the test case to the TDS source
- Tosca runs the test once per row, parameterizing each execution
Add rows for each test scenario:
| EmailAddress | Password | ExpectedResult |
|---|---|---|
| valid@example.com | Valid123! | Success |
| invalid@example.com | Wrong123! | Error: Invalid credentials |
| Valid123! | Error: Email required |
This separates test logic (the modules and test case structure) from test data (the specific values), making both easier to maintain.
Running Tests
From Tosca Commander:
- Select the TestSheet or execution list you want to run
- Click Run (or F5)
- Tosca opens the browser, executes each module, logs results
From Command Line (for CI):
# Tosca CI command line execution
ToscaCI.exe -workspace "C:\Tosca\MyProject" \
-list "RegressionSuite" \
-report "C:\Results"From Azure DevOps or Jenkins:
# Azure DevOps pipeline step
- task: PowerShell@2
displayName: 'Run Tosca Tests'
inputs:
script: |
& "C:\Program Files\TRICENTIS\Tosca Testsuite\ToscaCI\ToscaCI.exe" `
-workspace "$(TOSCA_WORKSPACE)" `
-list "$(TEST_LIST)" `
-report "$(Build.ArtifactStagingDirectory)\results"Reading Results
Tosca generates an HTML report and XML results after each run. The report includes:
- Pass/fail status per test case
- Execution duration
- Screenshots at the point of failure
- Module-level step results
Failed tests show which module attribute failed, which actual value was received vs. the expected value, and a timestamp for comparing against application logs.
Tosca vs. Code-Based Automation
Tosca is not the right choice for every team:
| Factor | Tosca | Selenium/Playwright |
|---|---|---|
| Setup time | High (module library) | Low (write tests directly) |
| Maintenance at scale | Low (update module once) | High (update every selector reference) |
| Technical skills required | Low | High |
| Flexibility | Lower (platform constraints) | High (full programming language) |
| Cost | High (enterprise license) | Free |
| Best for | Large teams, non-technical testers | Developer-led, startup teams |
For teams with 5–10 engineers who write tests themselves, Playwright or Robot Framework will ship tests faster. For organizations with dedicated QA teams, thousands of test cases, and a requirement for non-technical authoring, Tosca's model-based approach justifies the investment.
Limitations
Tosca requires a Windows environment — CI/CD on Linux is limited to Tosca Server scenarios. The license cost is significant (typically $10k–$50k+ per seat, enterprise pricing). And the platform lock-in is real: Tosca tests don't translate to other frameworks.
Smaller teams often find HelpMeTest provides a better balance — AI-powered test generation in plain English, no code required, cloud-hosted so no infrastructure to manage, with usage-based pricing instead of enterprise licensing.
Summary
Tricentis Tosca's model-based approach pays off at scale. Build a solid module library, separate test data from test logic using TDS, and compose test cases visually. The setup investment is real — plan for 2–4 weeks to build a reusable module library for a medium-complexity application. After that, test authoring velocity increases significantly as business users can write test cases without engineering support.