Tosca Terminologies: Modules, Test Cases, and Execution Lists
Tosca Terminologies: Modules, Test Cases, and Execution Lists
If you're new to Tricentis Tosca, understanding its core terminologies is the first step to mastering automated testing with this powerful tool.
In this blog, we’ll explain three of the most important Tosca concepts:
-
Modules
-
Test Cases
-
Execution Lists
Let’s break them down in simple terms with examples.
What Is Tosca?
Tosca is a model-based automated testing tool used for functional and regression testing.
It helps testers:
-
Design tests without scripting
-
Reuse test logic easily
-
Automate UI and API tests
-
Execute tests across platforms
1. Modules in Tosca
What is a Module?
A Module in Tosca is a representation of the UI or system element you want to test.
You can think of it as a map or template that tells Tosca:
“Here’s a button,” or “Here’s a textbox.”
Example:
You scan a login page. Tosca creates a Module with:
-
Username textbox
-
Password textbox
-
Login button
Each element in a Module is called a Module Attribute.
Types of Modules
| Type | Description |
|---|---|
| Standard Module | Created by scanning UI elements |
| Business Module | Custom reusable blocks for test logic |
| Technical Module | Lower-level technical operations |
Tip:
Use Module Names and attributes that clearly describe the UI element.
It helps in easy identification and reusability.
2. Test Cases in Tosca
What is a Test Case?
A Test Case is a sequence of test steps designed to verify a specific function or flow in your application.
In Tosca, Test Cases are created using Modules.
You drag Module Attributes into a Test Case and assign values or actions.
Example: Login Test Case
Modules Used:
-
LoginPage Module
Test Steps:
-
Type username =
testuser -
Type password =
123456 -
Click login button
Each step links back to the Module Attribute and tells Tosca what to do with it.
Why It’s Powerful
-
You don’t write code — just drag, drop, and assign.
-
You can reuse Modules across multiple Test Cases.
-
You can use Test Case Templates to run tests with different data sets.
3. Execution Lists in Tosca
What is an Execution List?
An Execution List is where you organize and run your Test Cases.
Think of it as a playlist of tests.
You decide:
-
Which Test Cases to run
-
In what order
-
With what settings
Example:
ExecutionList – LoginTests
-
TestCase 1 – Valid Login
-
TestCase 2 – Invalid Login
-
TestCase 3 – Blank Password
You can run the whole list or individual tests from it.
Execution Features
-
Schedule test runs
-
Generate logs and reports
-
Run tests in local or distributed environments
-
Integrate with CI/CD tools like Jenkins
Summary Table
| Term | Meaning | Role in Tosca |
|---|---|---|
| Module | Represents UI or system elements | Building block for Test Cases |
| Test Case | Sequence of test steps using Modules | Defines the test logic |
| Execution List | Group of Test Cases to run together | Organizes and runs tests |
💡 Real-Life Analogy
| Tosca Term | Real World Example |
|---|---|
| Module | Car parts (wheel, seat) |
| Test Case | Assembling a car to test drive |
| Execution List | Test drive schedule for cars |
🧠Tips for Beginners
-
Scan once, reuse forever – Don’t rescan the same screen again and again.
-
Name clearly – Use meaningful names for Modules and Test Cases.
-
Use folders – Organize your workspace using folders for features or modules.
-
Use TestCase Templates – For data-driven testing with multiple inputs.
Comments
Post a Comment