1.What is Tricentis Tosca?
Answer: Tosca is a continuous testing platform that supports end-to-end automation for software applications. It uses a Model-Based Test Automation (MBTA) approach.
Example: In a retail application, Tosca can automate login, product search, cart addition, and checkout process in one integrated test case.
2. What is Model-Based Testing in Tosca?
Answer: It involves creating reusable components (modules) from UI elements and using them in test cases instead of hardcoding steps.
Example: If you have a login screen, Tosca will scan it and create a reusable module for the username, password fields, and login button.
3. How do you create a test case in Tosca?
Answer: By dragging and dropping modules into a TestCase folder and assigning values to input fields or verifying outputs.
Example: Using a тАЬLoginтАЭ module, you input username and password in the TestCase steps.
4. What is a Tosca Module?
Answer: A module represents the UI elements or controls of an application (e.g., textbox, button) that Tosca scans for automation.
Example: Scanning a registration page will generate modules like “FirstName_Input,” “Email_Input,” and “Register_Button.”
5. How is Test Data handled in Tosca?
Answer: Using TestCase Design and Test Data Service to separate data from test cases, allowing for multiple combinations and reusability.
Example: Testing login with 10 different username-password combinations using the same module.
6. What is the difference between Technical and Business layers in Tosca?
Answer:
- Technical Layer: Contains the actual module structure (controls).
- Business Layer: Uses test cases and test data for execution.
Example: You scan a login page (technical layer), then use it in different test cases with various user credentials (business layer).
7. What is TBox in Tosca?
Answer: It is a set of standard modules and engines used in Tosca for automation actions (like clicking, typing, verifying).
Example: TBox Set Buffer can store dynamic values such as Order ID for future steps.
8. How do you verify data in Tosca?
Answer: By using the Verification action mode to compare expected vs actual values.
Example: After placing an order, you verify that the тАЬOrder ConfirmationтАЭ page is displayed with the correct order number.
9. What is a Buffer in Tosca
Answer: A temporary variable that stores dynamic values during execution.
Example: After logging in, you store the logged-in user’s name using a buffer and verify it on the homepage.
10. What is Steering in Tosca?
Answer: The process Tosca uses to interact with UI elements using identified controls and values.
Example: Tosca steers the “Search” input by entering a product name and clicking on the “Search” button.
11. What is the use of Test Configuration Parameters (TCP)?
Answer: Used to control the behavior of test cases dynamically, such as browser type or environment.
Example: Running the same test in Chrome and Firefox using different TCP values.
12. What is Reusability in Tosca?
Answer: Creating shared modules and test steps that can be reused across multiple test cases.
Example: A тАЬLoginтАЭ module is reused in 20 different test cases across various workflows.
13. What are ExecutionLists in Tosca?
Answer: A collection of test cases grouped for execution.
Example: You create an ExecutionList for all test cases related to the тАЬCheckoutтАЭ functionality.
14. How do you manage Test Results in Tosca?
Answer: Results are shown in Execution Logs, where you can track pass/fail status and error details.
Example: After execution, you view logs to identify a failure in the payment screen due to a missing credit card field.
15. What is the ScratchBook in Tosca?
Answer: A feature used to trial run test cases without affecting the main ExecutionList.
Example: You test a new test case in ScratchBook before adding it to a production suite.
16. What is the difference between Manual and Automated TestCases in Tosca?
Answer:
- Manual TestCases: Used for non-automatable tasks or documentation.
- Automated TestCases: Run by Tosca using modules and engines.
Example: A UI workflow is automated, while a hardware configuration check may be manual.
17. How do you handle dynamic objects in Tosca?
Answer: By using XPath, Regular Expressions, or Buffer to handle elements with changing IDs or values.
Example: An element ID like “btn_12345” is dynamically matched using regex or wildcards.
18. What is Tosca CI Integration?
Answer: Tosca supports Continuous Integration tools like Jenkins, Bamboo, etc., to run automated tests as part of pipelines.
Example: A nightly build in Jenkins triggers Tosca test execution and returns results.
19. What are Conditions and Loops in Tosca?
Answer: Tosca supports conditional logic (If-Else) and loops (While, ForEach) within test cases.
Example: If a user is already logged in, skip the login step and proceed to the dashboard.
20. How do you handle synchronization in Tosca?
Answer: Using WaitOn or Wait modules to wait for UI elements or application readiness.
Example: Wait for a loading spinner to disappear before clicking the тАЬSubmitтАЭ button.
