Section 1 – TOSCA Basics
1. What is TOSCA Automation Testing and why is it used?
Answer:
TOSCA is a model-based test automation tool from Tricentis that enables test automation for web, desktop, API, mobile, and BI apps without scripting.
- Reduces maintenance through reusable modules.
- Supports CI/CD pipelines for Agile/DevOps.
Example:
In a retail ERP migration, TOSCA automated 800 regression tests across SAP and web portals, cutting regression cycles from 10 days to 2 days.
2. What is Model-Based Test Automation (MBTA) in TOSCA?
Answer:
- Instead of writing scripts, TOSCA creates models of application screens/modules.
- Test cases are built by combining these reusable modules.
- When the application changes, updating the module updates all linked test cases.
Example:
A “Checkout” module was reused in 40 test cases for an e-commerce site. When the checkout button’s locator changed, updating it once fixed all tests.
3. What are Modules in TOSCA?
Answer:
Modules are collections of controls/elements that represent parts of the application under test.
- Created via scanning tools like XScan or API Scan.
- Can be linked to multiple test cases.
Snippet:
Module: LoginPage
- UsernameField
- PasswordField
- LoginButton4. What is TOSCA Commander?
Answer:
- The main interface where testers design test cases, manage execution lists, link requirements, and view results.
- Acts as the IDE for TOSCA.
5. Explain the TOSCA Workspace concept.
Answer:
- A workspace contains all modules, test cases, execution logs, and configurations.
- Can be Single-user (local) or Multi-user (connected to a repository).
6. What is the difference between TOSCA’s Standard Modules and Custom Modules?
Answer:
- Standard Modules: Pre-built by Tricentis (e.g., TBox Wait, Loop, If).
- Custom Modules: Created by scanning application UIs/APIs.
During TOSCA Training, learners are taught how to leverage both Standard and Custom Modules effectively to maximize test automation efficiency.
7. What is XScan in TOSCA?
Answer:
- The scanning utility to capture application controls for module creation.
- Supports desktop, web, SAP, and mobile.
Example:
Captured 12 SAP transaction screens into reusable modules for automated purchase order processing.
8. How does TOSCA handle object changes in applications?
Answer:
- Use Dynamic Identifiers or Parameterized Properties in modules.
- Update modules instead of all test cases when locators change.
9. What are Requirements in TOSCA?
Answer:
- Link business requirements to test cases for traceability.
- Requirement status changes based on linked test execution results.
10. What are ExecutionLists in TOSCA?
Answer:
- Groups of test cases for execution.
- Supports scheduling and parallel execution.
11. How do you execute TOSCA tests in different environments?
Answer:
- Use ExecutionList Configuration Parameters to set environment variables.
- Pass parameters via CI pipelines.
12. What are TestStepBlocks in TOSCA?
Answer:
- Groups of reusable TestSteps.
- Can be linked to multiple test cases.
Example:
A “Login” TestStepBlock reused in 30+ test cases.
13. Explain the role of TOSCA ScratchBook.
Answer:
- Allows ad-hoc execution of test steps without saving execution logs.
- Useful for debugging and module validation.
14. What is a TOSCA Template?
Answer:
- A parameterized TestCase used to generate multiple instances with different data sets.
- Supports data-driven testing.
15. How does TOSCA support manual testing?
Answer:
- TOSCA Commander allows creation of manual test cases.
- Testers execute them and log results for requirements traceability.
Section 2 – Test Case Design & Data-Driven Testing
16. How do you design a Test Case in TOSCA?
Answer:
- Identify reusable Modules.
- Drag & drop modules into the Test Case.
- Parameterize values for flexibility.
- Link with Requirements for traceability.
Example:
For a banking login test:
Step 1: Enter Username → Parameter: {BankUser}
Step 2: Enter Password → Parameter: {BankPass}
Step 3: Click Login
Step 4: Verify Dashboard → Expected: “Welcome”
17. What is Test Case Design (TCD) in TOSCA?
Answer:
- TCD separates test logic from test data.
- Use Classes and Instances in the TestCase-Design section.
- Instances generate test cases automatically.
Example:
Class: “Loan Application”
Instances:
- Applicant Age: 25, Loan Type: Home
- Applicant Age: 45, Loan Type: Personal
TOSCA will auto-create separate test cases for each combination.
18. How do you create parameterized Test Cases?
Answer:
- Use {ParameterName} syntax inside Test Steps.
- Link parameters to TestCase Design Instances or Excel data.
19. How do you import test data from Excel in TOSCA?
Answer:
- Use Excel Engine or TestSheet Import.
- Map Excel columns to test case parameters.
Snippet:
Excel:
| Username | Password | ExpectedMsg |
| user1 | pass1 | Welcome |
| user2 | pass2 | Access Denied |
20. What is the difference between Instances and Templates?
Answer:
- Template: A test case with placeholders for data.
- Instance: A concrete data set used to execute the template.
21. How do you manage large test data sets in TOSCA?
Answer:
- Store in TestSheets or external DB connections.
- Use Buffer for runtime storage.
22. What is a Buffer in TOSCA?
Answer:
- Temporary storage for values during execution.
- Useful for passing data between test steps or test cases.
Example:
Step 1: Capture Order ID → Store in OrderID buffer
Step 2: Search Order → Use {B[OrderID]}
23. How do you use If/Else conditions in TOSCA?
Answer:
- Use If → Condition → Else standard modules.
- Supports logical operators and parameter values.
Example:
If {Status} = Approved → Proceed to Payment
Else → Cancel Order
24. What are Loops in TOSCA?
Answer:
- Do-While or For Each loops to repeat steps for multiple items.
- Common in list processing.
Example:
Loop through all rows in a table until “Invoice” is found.
25. How do you reuse Test Steps in multiple Test Cases?
Answer:
- Use TestStepBlocks or Library Modules.
- Update once to reflect everywhere.
26. How do you implement data-driven testing in TOSCA?
Answer:
- Create Template Test Case.
- Link to a data source (Excel/TestSheet/DB).
- Generate multiple instances automatically.
27. What is the difference between Static and Dynamic Test Cases?
Answer:
- Static: Fixed test steps, no data variations.
- Dynamic: Steps generated based on data at runtime.
28. How do you validate dynamic content in TOSCA?
Answer:
- Use wildcards (*, ?) or regex in verification steps.
Example:
Expected: Welcome * → Matches “Welcome John”, “Welcome Admin”.
29. How do you link test cases to requirements?
Answer:
- Drag requirement to the test case or vice versa in Commander.
- Execution status updates the requirement’s pass/fail status.
30. How do you optimize data usage in TOSCA for performance?
Answer:
- Avoid hardcoding values.
- Use parameterization and buffers.
- Remove unused instances to reduce execution load.
Section 3 – TOSCA Execution & CI/CD Integration
31. How do you execute test cases in TOSCA?
Answer:
- Create ExecutionLists in TOSCA Commander.
- Drag the desired test cases into the list.
- Choose ExecutionMode: Manual, Automated, or Distributed.
Example:
For a regression suite, create ExecutionList_Regression and schedule it to run nightly via Tosca Distributed Execution (DEX).
32. What is Tosca Distributed Execution (DEX)?
Answer:
- DEX allows executing tests across multiple machines in parallel.
- Increases execution speed and efficiency for large suites.
Real-Time Use:
In a telecom project with 5,000+ test cases, DEX was set up on 8 agents, reducing execution time from 14 hours to 3 hours.
33. How do you schedule tests in TOSCA?
Answer:
- Use Tosca Execution Server Scheduler or integrate with Jenkins/ADO.
- Define frequency (daily, weekly, post-deployment).
Example:
Nightly smoke tests scheduled at 2 AM after CI builds.
34. How do you integrate TOSCA with Jenkins?
Answer:
- Install Tosca CI Client on Jenkins node.
- Use Jenkins “Execute Windows Batch Command”:
ToscaCIClient.exe –ExecutionList=”Regression_Suite” –ResultsDir=”C:\Reports”
- Publish results as HTML or JUnit reports.
35. What is the Tosca CI Client?
Answer:
- Command-line interface to trigger TOSCA executions.
- Supports execution lists, workspaces, and results export.
36. How do you pass parameters from Jenkins to TOSCA tests?
Answer:
- Use CI Parameters in ToscaCIClient.
Example:
ToscaCIClient.exe –Parameter:Env=QA –Parameter:Build=123
Inside TOSCA, {CP[Env]} and {CP[Build]} can be used.
37. How do you execute only failed test cases from the last run?
Answer:
- Use ExecutionList Filter → Status = Failed.
- Rerun only those in the next execution cycle.
38. How do you integrate TOSCA with Azure DevOps (ADO)?
Answer:
- Use Tosca Azure DevOps Extension or API calls.
- Map ADO pipelines to trigger ToscaCIClient commands.
39. How do you run TOSCA tests in a Docker container?
Answer:
- Create a Windows-based Docker image with Tosca CI Client installed.
- Jenkins/Azure can run the container for isolated executions.
40. How do you generate execution logs in TOSCA?
Answer:
- Right-click ExecutionList → “Export Execution Log”.
- Or use Tosca Reporting Server for HTML dashboards.
41. How do you execute API and UI tests together in TOSCA?
Answer:
- Combine API TestCases and UI TestCases into one ExecutionList.
- Ensure proper sequencing (API first, then UI validation).
42. How do you perform smoke testing in TOSCA?
Answer:
- Tag critical test cases with “Smoke”.
- Create an ExecutionList filtered by this tag.
43. How do you handle environment switching in execution?
Answer:
- Store environment details in TestConfigurationParameters (TCP).
- Change TCP value at execution time without editing test cases.
44. How do you send execution results to stakeholders automatically?
Answer:
- Enable “Email Notification” in DEX.
- Or have Jenkins pipeline email the exported HTML report after execution.
45. How do you handle long-running execution lists?
Answer:
- Break into smaller parallel execution lists.
- Use DEX Agents for a distributed run.
- Disable unnecessary logging for speed.
Section 4 – API Testing in TOSCA
46. What is API testing in TOSCA?
Answer:
- Validates REST, SOAP, GraphQL, or other service endpoints without UI.
- Ensures backend logic works correctly before UI is even built.
- Done using TOSCA API Scan & API Modules.
Example:
Testing POST /login endpoint for valid and invalid credentials before UI deployment.
47. How do you scan an API in TOSCA?
Answer:
- Open Tosca API Scan.
- Import WSDL (SOAP) or OpenAPI/Swagger (REST).
- API Scan generates modules (like UI modules).
- Drag them into TestCases.
48. How do you pass JSON body in an API request?
Answer:
- In API module’s RequestBody field, enter JSON text or parameterize it.
Snippet:
{
"username": "{UserName}",
"password": "{Password}"
}49. How do you validate API response in TOSCA?
Answer:
- Use Verify column for specific JSON/XML fields.
- Or use JsonPath/XPath expressions to target nested values.
Example:
Response:
{“status”:”success”,”id”:101}
Verify: status = success
50. How do you extract values from API responses?
Answer:
- Map response field to a Buffer for later use.
Example:
OrderID from API response stored in {B[OrderID]} → used in UI order tracking.
51. How do you handle API authentication in TOSCA?
Answer:
- Pass token in Headers (Bearer Token) or use Basic Auth fields in API module.
Example:
Header: Authorization: Bearer {AuthToken}
52. How do you chain multiple API calls in TOSCA?
Answer:
- Use output of first API (like an auth token or ID) as input to next API.
- Store intermediate results in buffers.
53. How do you parameterize API tests for multiple environments?
Answer:
- Store BaseURL in TCP (Test Configuration Parameter).
- Example: {CP[BaseURL]}/login works for QA, UAT, and Prod by changing TCP only.
54. How do you handle file uploads in API testing?
Answer:
- Use multipart/form-data in API module.
- Provide file path via parameter: {CP[FilePath]}.
55. How do you handle API timeouts or retries?
Answer:
- Use RetryOnError module.
- Configure WaitOn time and retry count in API request step.
56. How do you test SOAP services in TOSCA?
Answer:
- Import WSDL into API Scan.
- TOSCA auto-generates request templates with sample XML.
- Modify parameters and verify response tags.
57. How do you validate JSON arrays in TOSCA?
Answer:
- Use JsonPath with [*] selector.
Example:
Path: items[*].price → verifies price of all products in list.
58. How do you store API request/response logs?
Answer:
- Enable “SaveLog” in API Scan execution.
- Or export logs to HTML for reporting.
59. How do you mock APIs in TOSCA?
Answer:
- Use Tosca API Mock Server to simulate API responses when backend is unavailable.
Example:
Simulate GET /orders returning a fixed JSON response for UI testing.
60. How do you integrate API tests in CI/CD pipelines?
Answer:
- Trigger via ToscaCIClient in Jenkins/Azure before UI tests.
- Fail the build if any API test fails.
Section 5 – TOSCA Modules, Object Steering & Automation Best Practices
61. What is Object Steering in TOSCA?
Answer:
- Object Steering is Tosca’s way of identifying and interacting with UI elements during automation.
- Uses technical identifiers (XPaths, IDs, accessibility names) stored in Modules.
Real-Time Example:
When automating SAP, Tosca uses control IDs to uniquely steer a “Customer ID” input field even if its position changes.
62. How does Tosca identify UI objects?
Answer:
- Uses Steering Parameters from Modules, such as:
- TechnicalID (HTML id attribute)
- Caption (label text)
- Index (element position)
- TechnicalID (HTML id attribute)
63. What is XScan in Tosca?
Answer:
- XScan (Explorer Scan) is Tosca’s scanning tool for creating Modules.
- Supports technologies like HTML, SAP, Java, Mobile.
- Stores steering parameters for each control.
64. How do you scan a web page in Tosca?
Answer:
- Open XScan.
- Navigate to the page.
- Select elements → Save to Module folder.
- Use Module in TestCases.
65. What are Dynamic Identifiers in Tosca?
Answer:
- Element IDs that change every time (e.g., input_1234).
- Tosca handles them using Regular Expressions or Anchors in Module properties.
Example:
TechnicalID: input_\d+ matches any ID starting with input_ and followed by digits.
66. How do you handle dynamic tables in Tosca?
Answer:
- Use Row/Column identification with conditions like ProductName=Samsung.
- Tosca will automatically select that row regardless of its position.
67. How do you reuse Modules across projects?
Answer:
- Create a Common Module Library.
- Share via Tosca Repository or Workspace Import.
68. How do you handle popups in Tosca?
Answer:
- Scan popup window separately in XScan.
- Use Activate Window before interacting with controls.
69. How do you handle iframes in Tosca?
Answer:
- XScan detects iframe context.
- Ensure the Module contains the iframe switch info.
70. How do you handle controls that are not directly visible?
Answer:
- Scroll into view before interacting.
- Use steering parameter Visible=True.
71. How do you validate UI element properties?
Answer:
- Use Verify action mode on Module attribute like Enabled, Visible, Text.
72. What is Steering by Anchors?
Answer:
- Locating elements using nearby static text or controls.
- Useful when control IDs are dynamic but labels are fixed.
73. How do you handle multi-window applications?
Answer:
- Use Window Context in Modules.
- Activate specific window before performing action.
74. What is a TechnicalID in Tosca?
Answer:
- A unique identifier for a UI element used by Tosca to steer it.
- Stored in the Module definition.
75. How do you handle shadow DOM elements in Tosca?
Answer:
- Enable Shadow DOM Support in Tosca.
- Scan inside shadow roots in XScan.
76. How do you optimize Module scanning?
Answer:
- Scan only required controls, not the entire page.
- Use proper naming conventions.
77. How do you handle mobile automation in Tosca?
Answer:
- Use Tosca Mobile+ with Appium.
- Scan mobile screens via Mobile Scan.
78. What are Automation Best Practices in Tosca?
Answer:
- Modularize tests.
- Use TestCase Design (TCD) for reusability.
- Parameterize everything.
- Minimize maintenance by using anchors & regex.
79. How do you maintain large automation suites?
Answer:
- Organize Modules logically.
- Use Naming Conventions.
- Maintain common libraries separately.
80. How do you debug failed Tosca executions?
Answer:
- Check Execution Log details.
- Verify steering parameters in Modules.
- Rerun test in Debug mode to inspect step-by-step execution.
Section 6 – Advanced Tosca Features, Reporting & Real-Time Project Scenarios
81. What is Tosca BI Testing?
Answer:
- Tosca BI (Business Intelligence) Testing validates data transformations, ETL processes, and reports.
- Ensures data extracted from source matches what is loaded into target systems (e.g., Data Warehouse).
Example:
Verifying that sales figures in a Tableau dashboard match the raw transactional database.
82. How does Tosca perform BI testing?
Answer:
- Uses BI Modules for source & target data connections.
- Compares datasets at field, row, and aggregate levels.
83. How do you connect Tosca to a database?
Answer:
- Use Tosca DB Expert or ODBC connection.
- Execute SQL queries and validate results directly in TestSteps.
84. How do you perform ETL validation in Tosca?
Answer:
- Query source DB before ETL load.
- Query target DB after load.
- Compare using Tosca BI Compare feature.
85. What is Tosca Distributed Execution (DEX)?
Answer:
- Runs tests across multiple execution agents to reduce test time.
- Useful for large regression suites.
86. How do you set up Distributed Execution in Tosca?
Answer:
- Install Execution Agents on multiple machines.
- Configure DEX Server to distribute tests.
87. What is Tosca Commander?
Answer:
- The main desktop interface of Tosca where you create, manage, and execute tests.
88. What is Tosca Execution Log?
Answer:
- A detailed log of every executed step, with timestamps, screenshots, and results.
- Essential for debugging failures.
89. How do you capture screenshots in Tosca execution?
Answer:
- Enable Log Screenshot on Error in settings.
- Screenshots get attached to Execution Log.
90. How do you perform API & UI combined testing in Tosca?
Answer:
- Chain API calls to prepare data → Execute UI steps to verify it.
Example:
Create an order via API → Open web app and confirm order in UI.
91. What is the advantage of Tosca TCD (TestCase Design)?
Answer:
- Centralized test data management.
- Auto-generates multiple TestCases from one template.
92. How do you integrate Tosca with Jenkins?
Answer:
- Use Tosca CI Client in Jenkins pipeline.
- Run specific TestEvents and publish results.
93. How do you handle encrypted data in Tosca?
Answer:
- Use Crypto functions to encrypt/decrypt values.
- Store sensitive data securely in Tosca repository.
94. What is Tosca ScratchBook?
Answer:
- A test execution sandbox to run TestSteps instantly without affecting Execution Lists.
- Great for debugging a single TestCase.
95. How do you work with SAP applications in Tosca?
Answer:
- Use Tosca SAP Engine.
- Scan SAP GUI screens & steer controls using SAP-specific modules.
96. How do you manage test data across multiple environments?
Answer:
- Use Test Configuration Parameters (TCP) to switch URLs, DB connections, credentials based on environment.
97. How do you perform risk-based testing in Tosca?
Answer:
- Assign risk ratings to Requirements.
- Tosca auto-prioritizes high-risk areas during execution.
98. What is a real-time Tosca automation scenario you handled?
Answer:
- Scenario: Retail e-commerce platform had nightly UI & API tests.
- Tosca executed:
- API tests for product catalog sync.
- UI tests for checkout flow.
- BI tests for daily sales reports.
- API tests for product catalog sync.
- Integrated in Jenkins → results emailed to stakeholders daily.
99. How do you reduce Tosca test maintenance?
Answer:
- Use reusable Modules.
- Parameterize as much as possible.
- Use anchors for dynamic controls.
- Implement Common Library for all projects.
100. Why should a company adopt Tosca for automation?
Answer:
- Codeless automation speeds up onboarding.
- Supports UI, API, DB, BI, and Mobile testing in one tool.
- Strong integration with CI/CD.
- Lower maintenance costs compared to code-based frameworks.
