Tosca Interview Questions and Answers for Beginners

1) What is Tosca?
Tosca is one of the popular continuous testing platforms developed by Tricentis. It accelerates
testing with a no-code approach and script-less for end-to-end automation. This tool is used for both
functional and regression testing. In addition to the automation functions it offers, it also supports a
graphical user interface, application programming interface, and command-line interface.
It helps you to:
 Deliver fast feedback for DevOps and Agile
 Decreases regression testing time
 Maximizes maintainability and reusability
 Integrates and extends existing test assets

2) What are the main components of Tosca?

The major components available in Tosca are:
 Tosca Commander.
 Tosca Executor.
 Tosca XScan (Tosca Wizard)
 Test Repository.

3) What are the advantages of using Tosca?

The advantages of using the Tosca test suite are listed below:
 Multiple Features in One Tool
 Scriptless automation
 Suitable for large scale operations
 Test management
 Mass updates
 Reusability of assets
 Supports Multiple Platforms
 Quality Vendor Support
 Easy to use Interface
 Model-based automation
4) How to run Tests using ExecutionLists?
ExecutionLists in Tosca can be executed either by pressing the F6 key in the execution section or by
selecting the Run option from the context menu. Select the ExecutionLists of your choice using Ctrl +
left mouse button to run more than one ExecutionList. Check test object is already started before you
run the ExecutionLists.

5) What are the ways to run tests in the ScratchBook?

The ScratchBook allows you to perform trial runs for your test cases. Objects like
TestCases/TestCase folders and TestSteps can be run on this. The following options are available to
run tests in the ScratchBook:
 Run your objects immediately.
 Add or arrange objects in the ScratchBook and then run them
6) Explain the types of errors available in Tosca?
Mainly, there are three types of errors in Tosca.
 Verification-Failure: This occurs when verification does not provide the expected results. In
simple words, the value expected by the test case specification does not match the value
given by the test object.
 User Abort: Abort of the test execution by the user.
 Dialog-Failure: The application wants to get control of either that doesn’t exist or is not in an
operational state.

7) How will you fetch data from Excel using Tosca?

This can be done in two ways:
 For a single test scenario that has to be tested on various datasets, Tosca provides a feature
of TemplateInstances to create any number of test cases from your data set to import your
excel data and embed it in Test Case steps.
 To import data from an external source, you can use Excel Engine.

8) Explain how you can use multiple browsers within the same test case?
We need to automate a test case spanning various applications that run on multiple browsers. Using
buffers, change the Test Configuration Parameters at Run-Time by the following steps.
1. Change the Value of Test Configuration Parameter to {B[Browser]} or any other Buffer Name
you prefer
2. Use a TBOX Set Buffer to specify which Browser needs to be used
9) Explain about TC-Shell?
TC-Shell is the command-line control of the Tosca commander. It can be started in two different
modes using script and interactive.
 The script mode allows Shell to work with a set of commands from the script data file. This
mode is suitable for automation processes. The user has no possibility to intervene with any
section in this process.
 In interactive mode, the user will be provided with a set of options and assistance. Users can
use the complete range of functions of the GUI version in Tosca [Link] 50% OFF

10) Explain Test Data Management?

Test data management enables you to manage the test data needed for test execution. It is part of
the Tricentis Tosca Testsuite standard installation. It helps you to manage, use and reuse test data.
Testers can access the exact test data required seamlessly for even more complex scenarios, with
on-demand access to stateful test data.

11) What is the use of Tosca API Scan?

Tosca API Scan helps you to create TestCases for Tosca Orchestrated Service Virtualization or Web
Services. We can scan API definitions, validate messages and save them in TestCases.

12) What is Tosca Query Language?

TQL stands for Tosca Query Language, a powerful search method that allows you to take control of
the project at any time. The TQL search is context-dependent.
It is used for various functions and expressions within Tricentis Tosca.

13) What are the steps to perform Tosca Connect - HP ALM Tosca Integration?
The steps to perform Tosca Connect - HP ALM Tosca Integration are:
 Installation of REST API
 Installation of Tasktop with the License Key
 TestCases sync from TOSCA to Test Plan Module in HP ALM
 Execution List sync from TOSCA to Test Lab Module in HP ALM
 Execution Entry and Latest Test Result sync from TOSCA to Test Lab/Test Runs Modules in
HP ALM
14) What is the use of Tosca Jira Integration?
Tosca Jira integration improves the quality and traceability of software products. Some of the
benefits of this integration are:
 Synchronizes failed tests from Tosca
 Automatically reports defects.
 Supports cross-tool traceability.

15) What does Tosca CI do? And how can it be implemented?

Tosca continuous integration triggers the automated Tosca TestCases without user input. It helps to
reduce testing time for continuous integration and delivery.
Tosca CI can be implemented by either of the below-mentioned ways:
 Run the test execution via Remote Service through a separate execution workspace.
 Use Tosca Continuous Integration together with Tosca Distributed Execution.

Tosca Automation Interview Questions for Experienced

16) How does Tosca Testsuite support Model-Based And Risk-Based Testing?
Tosca defines test cases by scanning the applications. The automation model includes automation
logic for decoupling the test logic as specified as a test case. Once the required models are defined,
they can be used to execute both automated and manual test cases with input & verification data.

17) What are the various ways to identify objects in Tosca Testsuite?
The various ways to identify objects in Tosca Testsuite
 Identify by properties
 Identify by Anchor
 Identify by image
 Identify by index

18) Why should we use Rescan in Tosca?

Rescan is nothing but scanning the already scanned module. For suppose, you have a scanned web
page, but you need to make some changes and add new fields too. So to add them in the test case,
we need to rescan the module.
19) What is the use of ActionMode Constraint?
Action mode constraint is used for limiting the search. If a constraint is specified along with the verify,
it will verify only those items where the constraint is verified. You can use this if you know which
elements uniquely identify a list item.

20) Explain test configuration parameters?

Test configuration parameters help you to configure your tests to set values. It can also be used for
using Tosca objects.
You can create test configuration parameters for the following Tricentis Tosca objects:
 Project root element
 ExecutionList
 Component folder
 ExecutionEntry folder
 Configurations folder
 ExecutionEntry
 TestCase folder
 ScratchBook
 TestCase
 TestCase-Design folder
 ExecutionList folder

21) Explain String Operations?

String operations are used for verifying or modifying the strings using regular expressions. It includes
count specific characters/words in the statement, Replacing a word with another word, verifying the
format of some number, etc. You should have a module AidPack downloaded and imported into your
project to perform String operations.

22) Can we compare Pdf using Tosca?

Tosca provides us with a standard module to perform compare pdf. This function supports two pdf
files to be compared automatically with each other. If any differences are found they are shown in
ExecutionLog after the test execution.
23) How can you check if a file exists in a specific directory or not in Tosca?
Using “TBox File Existence”, we can check if the file exists in a specific directory or not. It contains
the following attributes:
1. Directory: Path to the file to be verified.
2. File: Name of the file to be verified. You can use ActionModes Verify or Walton.

24) Explain exploratory testing?

Exploratory testing is a process of designing and executing tests, and interpreting test results all at
one time. It is a plan-as-you-test approach. The purpose of this testing is to explore the unknown to
avoid unexpected results.

25) What is the advantage of linking test cases to requirements in Tosca Testsuite?
To keep track of the requirements we link the test cases in Tosca. This lets us know how many
requirements are covered, how many more are needed, and also to check for how many
requirements the test cases are passed successfully. This actually helps us to give a high-level
picture of requirement coverage.

26) How can you create TestCase templates manually?

We can create the TestCase templates using the provided modules of Tosca BI Modules And
Samples. tce subset.
Perform the following steps to create and use your own TestCase templates:
1. Create a TestCase according to your needs.
2. Right-click on the TestCase and select the option Convert to Template from the context menu
to convert the TestCase to a Template.
3. Drag the appropriate TestSheet and drop it onto your TestCase Template.
4. Use XL paths to manually assign the TestSheet values to the required TestStepValues
Instantiate the Testcase Template

27) How to instantiate TestCases with Excel?

Instantiating means changing one template test case into multiple test cases based on the test data
which is supplied to a template.
Perform the following steps to instantiate TestCases with excel:
1. The TestCase to be instantiated must be considered as a template.
 2. The values which need to be transferred from the template (parameters) must be linked by
specified syntax with attributes of the template.
3. Choose Create TemplateInstance from the context menu of the TestCase template.
4. The Excel file with the corresponding spreadsheet must be specified in the subsequent
dialog.
5. Confirm your inputs by clicking on the OK button.
6. Click on Yes in the subsequent dialog, and the instantiation process will start.

28) Which looping statements are available in Tosca?

To run TestSteps with branches,
Tosca supports IF, DO, and WHILE Statements.

29) Explain Synchronization In Tosca?

Synchronization means matching the application speed with automation tool speed. It can be
achieved in Tosca using ActionMode wait On. Synchronization settings are located under the
Settings->TBox->Synchronization:

30) Define business parameters in Tosca?

Business parameters allow you to steer the values you want in your test cases. Business
Parameters can also be updated if the payload has changed.
They can be defined manually within the module by the following:
 XML elements and attributes in the Payload tab
 JSON data in the Payload tab
 Headers in the Headers list
 Parameters in the Params tab
 Transport information in requests
 Status code and response time in responses

31) How do you explain Tosca Framework?

Tosca is one of the best and most popular automation tools provided by Tricentis. The Tosca tool
charges a specific price but offers equal services to use. Tosca has become popular because it gives
the proper balance between quality and performance. It delivers the full ability of the test cases for
providing an efficient test management process. It is suitable for large-scale applications to get
effective results.
32) What are the Limitations of the Tosca ScratchBook?
We use Tosca ScratchBook for storing the temporary execution logs. We use this option for the
temporary execution during the test case development to check the script accuracy. If we execute
the action repeatedly in a test step, the details will not be accessible. The execution logs also are not
stored permanently. So, Tosca ScratchBook is not a correct option to keep the execution logs.

25 Tosca interview questions

1. What is Tosca and how does it differ from other test automation tools?
2. Explain the concept of Model-Based Testing in Tosca.
3. How do you create a test case in Tosca?
4. Describe the process of creating a test suite in Tosca.
5. What are the different types of test steps available in Tosca?
6. How do you handle dynamic objects in Tosca?
7. Explain the purpose of the Tosca Repository.
8. What is the significance of the TestCase Design in Tosca?
9. How can you parameterize test cases in Tosca?
10. Describe how to use the Tosca API for test automation.
11. Write a simple Tosca test case to validate a login functionality with username and password as
parameters.
12. How do you integrate Tosca with CI/CD tools like Jenkins?
13. Explain the concept of Test Data Management in Tosca.
14. What are the different execution modes available in Tosca?
15. How do you perform data-driven testing in Tosca?
16. Write a Tosca script to navigate to a webpage and verify the title of the page.
17. How do you handle exceptions in Tosca test cases?
18. Explain the role of the Tosca Commander.
19. What is the purpose of the Tosca Execution List?
20. Write a Tosca test case to fill out a form and submit it, validating the success message.
 21. How do you implement version control in Tosca?
22. Describe how to use the Tosca TestCase Template feature.
23. Write a Tosca script to read data from an Excel file and use it in a test case.
24. How do you create reusable components in Tosca?
25. Explain how to generate reports in Tosca after test execution.
1. What is Tosca and how does it differ from other test automation tools?
Why you might get asked this: Interviewers often ask "What is Tosca and how does it differ from other test
automation tools?" to gauge your foundational understanding of Tosca and its unique features, ensuring you
can effectively leverage it in a software testing role, such as a Test Automation Engineer.
How to answer:
Start by defining Tosca as a comprehensive test automation tool designed for end-to-end testing.
Highlight its model-based testing approach, which simplifies test case creation and maintenance.
Compare its unique features, such as scriptless automation and robust test data management, with other tools.
Example answer:
"Tosca is a comprehensive test automation tool designed for end-to-end testing, known for its model-based
testing approach that simplifies test case creation and maintenance. Unlike other tools, Tosca offers scriptless
automation and robust test data management, making it highly efficient and user-friendly."
2. Explain the concept of Model-Based Testing in Tosca.
Why you might get asked this: Interviewers might ask you to "Explain the concept of Model-Based Testing in
Tosca" to assess your understanding of Tosca's core methodology, which is crucial for roles like Test
Automation Engineer that require efficient test case design and maintenance.
How to answer:
Define Model-Based Testing as a method that uses models to represent the desired behavior of a system.
Explain how Tosca uses these models to automatically generate and maintain test cases.
Highlight the benefits, such as reduced maintenance effort and improved test coverage.
Example answer:
"Model-Based Testing in Tosca involves using models to represent the desired behavior of a system, which
Tosca then uses to automatically generate and maintain test cases. This approach reduces maintenance effort
and improves test coverage, making the testing process more efficient."
3. How do you create a test case in Tosca?
Why you might get asked this: Interviewers might ask "How do you create a test case in Tosca?" to evaluate
your practical skills in using the tool for test automation, ensuring you can effectively contribute to the testing
process, for example, as a Test Automation Engineer.
How to answer:
Begin by explaining the initial step of creating a new test case in Tosca Commander.
Describe how to add test steps by dragging and dropping modules from the Tosca Repository.
Conclude by mentioning the importance of parameterizing the test steps for reusability and flexibility.
Example answer:
"To create a test case in Tosca, start by opening Tosca Commander and creating a new test case. Then, add test
steps by dragging and dropping modules from the Tosca Repository, ensuring to parameterize them for
reusability and flexibility."
4. Describe the process of creating a test suite in Tosca.
Why you might get asked this: Interviewers might ask you to "Describe the process of creating a test suite in
Tosca" to assess your ability to organize and manage multiple test cases efficiently, which is crucial for roles
like Test Automation Engineer that require comprehensive test planning and execution.
How to answer:
Start by explaining the creation of a new test suite in Tosca Commander.
Describe how to add existing test cases to the test suite for organized execution.
Conclude by mentioning the importance of configuring execution settings for the test suite.
Example answer:
"To create a test suite in Tosca, start by opening Tosca Commander and creating a new test suite. Then, add
existing test cases to the test suite and configure the execution settings for organized and efficient test
execution."
5. What are the different types of test steps available in Tosca?
Why you might get asked this: Interviewers might ask "What are the different types of test steps available in
Tosca?" to evaluate your detailed knowledge of Tosca's functionalities, ensuring you can effectively utilize its
various test steps for comprehensive test automation, for example, as a Test Automation Engineer.
How to answer:
Begin by categorizing the test steps into basic, conditional, and loop types.
Explain the purpose of each category, such as basic steps for simple actions and conditional steps for decision-
making.
Highlight examples of each type, like input steps for basic, if-else for conditional, and for-each loops for loop
types.
Example answer:
"Tosca offers various types of test steps, including basic steps for simple actions, conditional steps for
decision-making, and loop steps for repetitive actions. Examples include input steps for basic actions, if-else
steps for conditional logic, and for-each loops for iterating over data sets."
6. How do you handle dynamic objects in Tosca?
Why you might get asked this: Interviewers might ask "How do you handle dynamic objects in Tosca?" to
assess your ability to manage and automate tests involving elements that change frequently, which is crucial for
roles like Test Automation Engineer that require adaptability and precision in dynamic testing environments.
How to answer:
Explain the use of Tosca's dynamic object identification methods.
Mention the importance of using regular expressions for dynamic properties.
Highlight the role of Tosca's anchor and buffer functionalities in handling dynamic objects.
Example answer:
"To handle dynamic objects in Tosca, I use Tosca's dynamic object identification methods and regular
expressions for dynamic properties. Additionally, I leverage Tosca's anchor and buffer functionalities to ensure
accurate identification and interaction with dynamic elements."
7. Explain the purpose of the Tosca Repository.
Why you might get asked this: Interviewers might ask "Explain the purpose of the Tosca Repository" to
evaluate your understanding of Tosca's central storage system for test artifacts, ensuring you can effectively
manage and reuse test components, for example, as a Test Automation Engineer.
How to answer:
Start by defining the Tosca Repository as a central storage system for all test artifacts.
Explain its role in enabling reusability and efficient management of test components.
Highlight how it facilitates collaboration among team members by providing a shared resource.
Example answer:
"The Tosca Repository is a central storage system for all test artifacts, enabling reusability and efficient
management of test components. It also facilitates collaboration among team members by providing a shared
resource."
8. What is the significance of the TestCase Design in Tosca?
Why you might get asked this: Interviewers might ask "What is the significance of the TestCase Design in
Tosca?" to evaluate your understanding of how well-structured test case design can enhance test efficiency and
maintainability, which is crucial for roles like Test Automation Engineer that require meticulous planning and
execution of test cases.
How to answer:
Define TestCase Design as a structured approach to creating and organizing test cases.
Explain how it enhances test efficiency by promoting reusability and reducing redundancy.
Highlight its role in improving maintainability by providing a clear and organized framework for test cases.
Example answer:
"TestCase Design in Tosca is crucial as it promotes reusability and reduces redundancy, enhancing overall test
efficiency. It also improves maintainability by providing a clear and organized framework for test cases,
making them easier to manage and update."
9. How can you parameterize test cases in Tosca?
Why you might get asked this: Interviewers might ask "How can you parameterize test cases in Tosca?" to
assess your ability to create flexible and reusable test cases, which is crucial for roles like Test Automation
Engineer that require efficient test management and execution.
How to answer:
Explain the use of Tosca's TestCase Design Section for parameterization.
Mention the importance of defining parameters in the TestCase Template.
Highlight how to link the parameters to test steps for dynamic data input.
Example answer:
"To parameterize test cases in Tosca, I use the TestCase Design Section to define parameters in the TestCase
Template. Then, I link these parameters to test steps, allowing for dynamic data input and flexible test
execution."
10. Describe how to use the Tosca API for test automation.
Why you might get asked this: Interviewers might ask "Describe how to use the Tosca API for test automation"
to evaluate your ability to integrate Tosca with other systems and automate complex workflows, which is
crucial for roles like Test Automation Engineer that require advanced technical skills and seamless tool
integration.
How to answer:
Start by explaining the purpose of the Tosca API in enabling integration with other systems.
Mention the steps to set up and configure the Tosca API for test automation.
Highlight the use of API commands to execute and manage test cases programmatically.
Example answer:
"To use the Tosca API for test automation, you first need to set up and configure the API by following the
official documentation. Once configured, you can use API commands to execute and manage test cases
programmatically, ensuring seamless integration with other systems."
11. Write a simple Tosca test case to validate a login functionality with username and password as
parameters.
Why you might get asked this: Interviewers might ask you to "Write a simple Tosca test case to validate a login
functionality with username and password as parameters" to assess your practical skills in creating and
executing test cases, ensuring you can effectively handle real-world scenarios, for example, as a Test
Automation Engineer.
How to answer:
Start by explaining the creation of a new test case in Tosca Commander.
Describe how to add test steps for entering the username and password.
Conclude by mentioning the validation step to check the login success message.
Example answer:
"To validate a login functionality in Tosca, create a new test case and add test steps to input the username and
password parameters. Finally, include a validation step to check for the login success message."
12. How do you integrate Tosca with CI/CD tools like Jenkins?
Why you might get asked this: Interviewers might ask "How do you integrate Tosca with CI/CD tools like
Jenkins?" to evaluate your ability to streamline automated testing within a continuous integration and delivery
pipeline, which is crucial for roles like Test Automation Engineer that require efficient and seamless
deployment processes.
How to answer:
Explain the installation and configuration of the Tosca CI/CD integration plugin.
Mention the steps to create and configure a Jenkins job for Tosca test execution.
Highlight the importance of setting up reporting and notifications for test results.
Example answer:
"To integrate Tosca with CI/CD tools like Jenkins, first install and configure the Tosca CI/CD integration
plugin. Then, create and configure a Jenkins job to execute Tosca tests, ensuring to set up reporting and
notifications for test results."
13. Explain the concept of Test Data Management in Tosca.
Why you might get asked this: Interviewers might ask "Explain the concept of Test Data Management in
Tosca" to evaluate your ability to efficiently handle and utilize test data, which is crucial for roles like Test
Automation Engineer that require precise and organized data management.
How to answer:
Define Test Data Management as the process of handling and organizing test data efficiently.
Explain how Tosca uses data sheets and templates to manage test data.
Highlight the benefits of centralized test data management, such as consistency and reusability.
Example answer:
"Test Data Management in Tosca involves efficiently handling and organizing test data using data sheets and
templates. This centralized approach ensures consistency and reusability, making the testing process more
streamlined and effective."
14. What are the different execution modes available in Tosca?
Why you might get asked this: Interviewers might ask "What are the different execution modes available in
Tosca?" to evaluate your understanding of Tosca's flexibility in test execution, ensuring you can effectively
utilize various modes for different testing scenarios, for example, as a Test Automation Engineer.
How to answer:
Start by listing the different execution modes available in Tosca, such as Manual, Automated, and Hybrid.
Explain the purpose of each mode, highlighting their unique features and use cases.
Conclude by mentioning the flexibility Tosca offers in switching between these modes based on testing
requirements.
Example answer:
"Tosca offers different execution modes such as Manual, Automated, and Hybrid. Each mode serves unique
purposes, providing flexibility to switch based on testing requirements."
15. How do you perform data-driven testing in Tosca?
Why you might get asked this: Interviewers might ask "How do you perform data-driven testing in Tosca?" to
evaluate your ability to efficiently manage and execute tests with varying data sets, which is crucial for roles
like Test Automation Engineer that require robust and scalable testing solutions.
How to answer:
Explain the use of Tosca's TestCase Design Section to define data sources.
Mention how to link test cases to these data sources for dynamic input.
Highlight the benefits of using data-driven testing for comprehensive test coverage.
Example answer:
"To perform data-driven testing in Tosca, I use the TestCase Design Section to define data sources and link test
cases to these sources for dynamic input. This approach ensures comprehensive test coverage and efficient test
execution."
16. Write a Tosca script to navigate to a webpage and verify the title of the page.
Why you might get asked this: Interviewers might ask you to "Write a Tosca script to navigate to a webpage
and verify the title of the page" to assess your practical scripting skills and ability to automate web interactions,
which is crucial for roles like Test Automation Engineer that require hands-on experience with Tosca.
How to answer:
Start by explaining the creation of a new test case in Tosca Commander.
Describe how to add test steps for navigating to the webpage and capturing the title.
Conclude by mentioning the validation step to compare the captured title with the expected title.
Example answer:
"To navigate to a webpage and verify the title in Tosca, create a new test case and add steps to open the
browser and navigate to the URL. Then, capture the page title and validate it against the expected title."
17. How do you handle exceptions in Tosca test cases?
Why you might get asked this: Interviewers might ask "How do you handle exceptions in Tosca test cases?" to
evaluate your problem-solving skills and ability to ensure robust test execution, which is crucial for roles like
Test Automation Engineer that require effective error management and recovery strategies.
How to answer:
Explain the use of Tosca's built-in exception handling mechanisms.
Mention the importance of defining custom recovery scenarios for specific exceptions.
Highlight the role of logging and reporting in identifying and resolving exceptions.
Example answer:
"To handle exceptions in Tosca test cases, I utilize Tosca's built-in exception handling mechanisms and define
custom recovery scenarios for specific exceptions. Additionally, I rely on detailed logging and reporting to
identify and resolve exceptions efficiently."
18. Explain the role of the Tosca Commander.
Why you might get asked this: Interviewers might ask "Explain the role of the Tosca Commander" to evaluate
your understanding of Tosca's central interface for managing test cases, which is crucial for roles like Test
Automation Engineer that require comprehensive test management and execution capabilities.
How to answer:
Define Tosca Commander as the central interface for managing all test activities.
Explain its role in organizing test cases, test data, and execution lists.
Highlight its importance in providing a unified platform for collaboration and reporting.
Example answer:
"Tosca Commander is the central interface for managing all test activities, including organizing test cases, test
data, and execution lists. It provides a unified platform for collaboration and reporting, ensuring efficient and
streamlined test management."
19. What is the purpose of the Tosca Execution List?
Why you might get asked this: Interviewers might ask "What is the purpose of the Tosca Execution List?" to
evaluate your understanding of how to organize and manage test executions efficiently, which is crucial for
roles like Test Automation Engineer that require meticulous planning and execution of automated tests.
How to answer:
Define the Tosca Execution List as a tool for organizing and managing test executions.
Explain its role in scheduling and executing test cases systematically.
Highlight its importance in tracking and reporting test execution results.
Example answer:
"The Tosca Execution List is a tool for organizing and managing test executions, ensuring systematic
scheduling and execution of test cases. It plays a crucial role in tracking and reporting test execution results,
providing valuable insights for continuous improvement."
20. Write a Tosca test case to fill out a form and submit it, validating the success message.
Why you might get asked this: Interviewers might ask you to "Write a Tosca test case to fill out a form and
submit it, validating the success message" to assess your practical skills in automating form submissions and
verifying outcomes, which is crucial for roles like Test Automation Engineer that require hands-on experience
with Tosca.
How to answer:
Start by explaining the creation of a new test case in Tosca Commander.
Describe how to add test steps for filling out the form fields and submitting the form.
Conclude by mentioning the validation step to check for the success message.
Example answer:
"To fill out a form and submit it in Tosca, create a new test case and add steps to input data into the form fields.
Finally, include a validation step to check for the success message after submission."
21. How do you implement version control in Tosca?
Why you might get asked this: Interviewers might ask "How do you implement version control in Tosca?" to
evaluate your ability to manage and track changes in test artifacts, which is crucial for roles like Test
Automation Engineer that require maintaining the integrity and history of test cases.
How to answer:
Explain the use of Tosca's built-in version control system for tracking changes.
Mention the importance of regularly committing changes to maintain a history of test artifacts.
Highlight the role of branching and merging in managing different versions of test cases.
Example answer:
"To implement version control in Tosca, I use Tosca's built-in version control system to track changes and
regularly commit updates to maintain a history of test artifacts. Additionally, I utilize branching and merging to
manage different versions of test cases effectively."
22. Describe how to use the Tosca TestCase Template feature.
Why you might get asked this: Interviewers might ask "Describe how to use the Tosca TestCase Template
feature" to evaluate your ability to create reusable and scalable test cases, which is crucial for roles like Test
Automation Engineer that require efficient test management and execution.
How to answer:
Explain the purpose of the TestCase Template in creating reusable test cases.
Mention the steps to define parameters and link them to test steps within the template.
Highlight the benefits of using templates for efficient and scalable test case management.
Example answer:
"To use the Tosca TestCase Template feature, start by defining parameters and linking them to test steps within
the template. This approach ensures reusability and scalability, making test case management more efficient."
23. Write a Tosca script to read data from an Excel file and use it in a test case.
Why you might get asked this: Interviewers might ask you to "Write a Tosca script to read data from an Excel
file and use it in a test case" to evaluate your ability to handle data-driven testing scenarios, which is crucial for
roles like Test Automation Engineer that require efficient data management and test execution.
How to answer:
Explain the process of importing the Excel file into Tosca.
Mention how to map the Excel data to Tosca test case parameters.
Highlight the execution of the test case using the imported data.
Example answer:
"To read data from an Excel file in Tosca, first import the Excel file into Tosca and map the data to test case
parameters. Then, execute the test case using the imported data to ensure dynamic and data-driven testing."
24. How do you create reusable components in Tosca?
Why you might get asked this: Interviewers might ask "How do you create reusable components in Tosca?" to
evaluate your ability to optimize test automation by creating modular and maintainable test components, which
is crucial for roles like Test Automation Engineer that require efficient and scalable testing solutions.
How to answer:
Explain the use of Tosca's module-based approach for creating reusable components.
Mention the importance of defining clear and generic actions within these modules.
Highlight the benefits of reusability in reducing maintenance effort and improving test efficiency.
Example answer:
"To create reusable components in Tosca, I use Tosca's module-based approach to define clear and generic
actions within these modules. This ensures that the components are easily maintainable and can be reused
across multiple test cases, significantly reducing maintenance effort and improving test efficiency."
25. Explain how to generate reports in Tosca after test execution.
Why you might get asked this: Interviewers might ask "Explain how to generate reports in Tosca after test
execution" to evaluate your ability to effectively communicate test results and insights, which is crucial for
roles like Test Automation Engineer that require clear and comprehensive reporting for stakeholders.
How to answer:
Start by explaining the use of Tosca's built-in reporting features.
Mention the steps to configure and customize the report settings.
Highlight the importance of exporting and sharing the reports with stakeholders.
Example answer:
"To generate reports in Tosca after test execution, I use Tosca's built-in reporting features to configure and
customize the report settings. Then, I export and share the reports with stakeholders to ensure clear
communication of test results and insights."
 Tosca Intermediate Interview Questions and Answers

These questions are a little trickier. They test how well you can use Tosca in real work situations.

1) Explain the Tosca Query Language (TQL).

Tosca Query Language (TQL) is a powerful tool for searching and filtering objects within Tosca. It
uses SQL-like syntax to define search criteria. For example, to find all test cases with a specific
name, you can use:

sql

SELECT * FROM TestCase WHERE Name = ‘My Test Case’

TQL supports various operators like =, <>, >, <, LIKE, IN, and BETWEEN. You can also use logical
operators AND, OR, and NOT. TQL is used extensively in Tosca for filtering objects in the repository,
defining search criteria in execution lists, and configuring test data.

2) What are the different ways to create test cases in Tosca?

Tosca offers several methods to create test cases:

Manual creation: You can create test cases from scratch by defining steps, parameters, and
expected results.

 Recording: Tosca’s recording capabilities allow you to record user interactions with the
application and generate test cases automatically.
 Scanning: Tosca can scan the application under test to identify objects and generate test
cases based on the object hierarchy.
 Importing: Test cases can be imported from external sources like Excel sheets or XML files.
 Conversion: Existing test cases can be converted to templates or reusable modules for
creating new test cases.
3) Explain the Tosca recovery scenario.
When a test case fails in Tosca, it triggers the recovery scenario. Tosca attempts to recover from the
failure based on the configured recovery actions. Recovery actions can include:

 Retrying the failed step

 Executing alternative steps
 Navigating to a specific page
 Logging the failure and continuing the test
Recovery scenarios are defined at the project, module, or test case level. Tosca provides a visual
editor to configure recovery actions. If the recovery scenario is unable to resolve the failure, the test
case is marked as failed, and the execution continues to the next test case.
4) What is the significance of Tosca’s Risk-Based Testing approach?
Tosca’s Risk-Based Testing approach helps prioritise testing efforts based on the risk associated
with each requirement or test case. Risk factors considered include:

 Business impact
 Technical complexity
 Frequency of use
 Defect history
Tosca calculates a risk score for each requirement and test case based on these factors. The risk
score is used to prioritise test execution, allocate testing resources, and identify high-risk areas that
require more thorough testing.

5) How does Tosca support data-driven testing?

Tosca supports data-driven testing using various data sources:

 Excel sheets: Test data can be stored in Excel sheets, and Tosca can read the data during
test execution.
 Databases: Tosca can connect to databases and fetch test data directly from tables.
 XML files: Test data can be stored in XML files and used in Tosca test cases.
 Datasheets: Tosca provides built-in datasheets to store and manage test data.
Test data is mapped to test case parameters, allowing the same test case to be executed with
different data sets. This approach enhances test coverage and reduces maintenance effort.

6) What are the different types of reports generated in Tosca?

Tosca generates various types of reports to analyse test results:

 Execution logs: Detailed logs are generated for each test execution, capturing step-by-step
execution details.
 Detailed reports: Comprehensive reports are generated for each test case, including test
steps, parameters, and results.
 Summary reports: High-level reports summarise the overall test execution, providing an
overview of passed, failed, and blocked test cases.
 Trend reports: Trend reports analyse test results over time, highlighting improvements or
regressions.
 Requirement coverage reports: These reports track the coverage of requirements by test
cases.
Reports can be customised, filtered, and exported in various formats like PDF, HTML, and Excel.

7) How does Tosca integrate with CI/CD pipelines?

Tosca integrates with CI/CD pipelines through Tosca CI, a command-line interface for automating
test execution. Tosca CI allows you to:

 Run tests from the command line without using the Tosca GUI.
 Schedule and trigger test executions based on events like code commits or nightly builds.
  Integrate with popular CI tools like Jenkins, Azure DevOps, and Travis CI.
 Capture test results and generate reports for further analysis.
By integrating Tosca with CI/CD pipelines, you can achieve continuous testing, ensuring that new
code changes do not break existing functionality.

You can handle the basics and some of the more difficult questions. Let’s try some really hard ones
now.

Tosca Advanced Interview Questions and Answers

Get ready for the tough questions! These are for people who know Tosca very well.

1) Explain Tosca’s Model-Based Test Automation (MBTA) approach.

Tosca’s MBTA approach differs from traditional script-based testing. Instead of coding test
scripts, you create a business-readable automation model by scanning the application’s UI or APIs.
This model acts as reusable “Lego blocks” that you can combine to create test cases. When the
application changes, you only need to update the affected modules. The changes are automatically
synchronised across all impacted test cases. This makes test maintenance much faster and less
error-prone compared to script-based testing.

2) How does Tosca handle dynamic objects?

Tosca provides techniques to identify and interact with objects that change attributes during test
execution. You can use a combination of object properties, such as ID, name, and position, to create
unique identifiers for dynamic objects. Tosca also allows you to modify and adapt these identifiers to
ensure consistent and accurate object recognition, even as the application changes. This helps
maintain the resilience and reliability of your automated tests.

3) What is Tosca’s approach to test case maintenance and version control?

Tosca offers features for managing test case changes and revisions. When you save a test case
with new changes, the version number automatically increases. You can only make changes based
on the latest version of the test case, and previous versions are tracked in the history. Tosca also
allows you to approve test cases, ensuring that only the approved versions are used for test
execution. This version control system helps you maintain and update your test cases as the
application evolves.

4) How can you create custom modules in Tosca?

Tosca allows you to develop specialised modules for specific technologies. You can create custom
modules by scanning the application’s UI or APIs and defining the necessary object identifiers and
actions. These modules can then be reused across multiple test cases, saving time and effort.
Tosca’s modular approach enables you to build a library of common workflows, test sequences, and
test cases that can be easily adapted and reused.
5) How does Tosca support API testing?
Tosca provides the API Scan feature, which allows you to easily create, manage, and execute
automated API tests. You can scan the API endpoints, define the request parameters and expected
responses, and then incorporate the API tests into your overall test automation strategy. Tosca’s API
testing capabilities enable you to validate the functionality and integration of your application’s APIs,
ensuring a comprehensive testing approach.

6) What are Tosca’s capabilities for test data management?

Tosca combines test data management and Test Data Service (TDS) to help teams create, design,
locate, manage, and provision test data efficiently. This addresses the common challenge of testers
spending significant time finding and creating test data manually. Tosca’s TDM features allow you to
generate, mask, and provision the necessary test data on-the-fly, improving the speed and reliability
of your testing process.

7) How can you optimise the performance of Tosca test execution?

To optimise Tosca test execution, you can follow several best practices:

 Organise your test artefacts in a logical folder structure for better maintainability.
 Use the right object identifiers to ensure reliable object recognition.
 Create modular and reusable test cases to maximise your work.
 Implement wait times to handle slow application responses or dependencies.
 Perform trial runs of your test cases to identify and fix any instabilities.
 Organise your execution lists for efficient test runs.
By following these practices, you can improve the overall performance and reliability of your Tosca
test automation.

8) What are some common challenges faced in Tosca automation and how do you address
them?
Some common challenges in Tosca automation include:

 Object Identification: Dynamic objects with changing attributes can be difficult to identify.
Address this by using a combination of object properties and adapting identifiers as the
application changes.
 Test Maintenance: As the application evolves, keeping test cases up-to-date can be time-
consuming. Tosca’s model-based approach and version control features help streamline test
case maintenance.
 Test Reliability: Flaky tests due to slow application responses or dependencies can cause
issues. Implement wait times and perform trial runs to improve test reliability.
 Test Data Management: Manually creating and managing test data can be a bottleneck.
Utilise Tosca’s test data management capabilities to generate, mask, and provision test data
efficiently.
 Performance Optimization: Poorly organised test artefacts and execution lists can affect test
execution performance. Follow Tosca’s best practices for folder structure, module design, and
execution list management.
Tosca Behavioral & Scenario-Based Interview Questions and
Answers

These questions help the interviewer get to know how you work and how you solve problems.

1) Describe a complex test automation scenario you handled with Tosca.

I once worked on automating the testing of a complex enterprise application with multiple modules
and integrations. The application had a web-based user interface, REST APIs, and a database
backend. To handle this, I leveraged Tosca’s capabilities to create a comprehensive test automation
framework.

First, I used Tosca’s model-based testing approach to map out the application’s various components
and their relationships. This allowed me to design test cases that covered end-to-end user journeys,
including UI interactions, API calls, and database validations.

Next, I created reusable Tosca modules for common actions, such as user authentication, data
manipulation, and API requests. This improved test case maintainability and reduced duplication of
effort.

To handle the application’s dynamic nature, I incorporated Tosca’s data-driven testing capabilities. I
parameterized test data, allowing me to easily update and expand test scenarios as the application
evolved.

Tosca’s integration with other tools, like defect tracking systems, proved invaluable. When tests
failed, Tosca automatically logged detailed bug reports, streamlining the collaboration with the
development team.

Overall, Tosca’s comprehensive features enabled me to create a robust and scalable test
automation solution, which significantly improved the quality and release cadence of the enterprise
application.

2) How have you used Tosca to improve testing efficiency or test coverage?
In one of my previous projects, I used Tosca to enhance the testing efficiency and coverage of a
complex web application. The application had a large number of user scenarios, and manual testing
was becoming increasingly time-consuming and error-prone.

To address this, I leveraged Tosca’s scriptless automation capabilities to create a comprehensive

test suite that covered the application’s critical user flows. By using Tosca’s intuitive interface and
visual modelling tools, I was able to quickly design and implement test cases without the need for
extensive programming knowledge.

Tosca’s modular test case design allowed me to create reusable components, which I could easily
combine to cover a wide range of scenarios. This approach not only improved test case
maintainability but also reduced the overall test creation time.
Furthermore, Tosca’s integration with various data sources enabled me to implement data-driven
testing. I was able to parameterize test data, allowing me to expand test coverage and identify edge
cases more effectively.

Another key aspect was Tosca’s seamless integration with the application’s CI/CD pipeline. I set up
automated test execution as part of the build and deployment process, ensuring that every code
change was thoroughly tested before being released to production. This helped us catch regressions
early and improve the overall quality of the application.

By leveraging Tosca’s capabilities, I was able to significantly improve the testing efficiency and
coverage of the web application, leading to a more robust and reliable product.

3) Tell me about a time you had to troubleshoot a Tosca test failure.

In one of my projects, I encountered a complex Tosca test failure that required in-depth
troubleshooting. The test case was designed to validate the functionality of a critical user workflow in
a web-based enterprise application.

During the test execution, the test case failed unexpectedly, and I needed to investigate the root
cause. I started by reviewing the test logs and the Tosca execution report, which provided valuable
insights into the failure.

The initial analysis revealed that the test failure was related to an element identification issue. Tosca
was unable to locate a specific UI element on the page, causing the test to fail. I suspected that the
application’s UI had undergone some changes, leading to the identification problem.

To troubleshoot the issue, I first checked the Tosca module associated with the failed test case. I
verified that the element locators were still valid and that the module was up-to-date. However,
further investigation revealed that the application’s UI had indeed been updated, and the existing
locators were no longer accurate.

I then used Tosca’s Rescan feature to update the module and capture the new element locators.
This process involved manually verifying the updated locators and ensuring that they were correctly
mapped to the corresponding UI elements.

After updating the module, I re-executed the test case and observed that it passed successfully. To
ensure the long-term stability of the test case, I also reviewed the other test cases in the suite that
were dependent on the same UI elements and updated them accordingly.

By leveraging Tosca’s troubleshooting capabilities, I was able to identify and resolve the root cause
of the test failure, ensuring the continued reliability of the test automation framework.

4) How do you ensure the reusability and maintainability of Tosca test cases?
Ensuring the reusability and maintainability of Tosca test cases is crucial for the long-term success
of any test automation initiative. Here are some strategies I have employed to achieve this:

Modular Test Case Design

I strongly believe in the importance of a modular approach to test case design. I create reusable
Tosca modules for common actions, such as user authentication, data manipulation, and API
interactions. This allows me to build test cases by combining these modular components, reducing
duplication and improving maintainability.

Parameterization and Data-Driven Testing

Tosca’s data-driven testing capabilities are invaluable for maintaining test cases. I parameterize test
data, such as user credentials, input values, and expected results. This allows me to easily update
and expand test scenarios as the application evolves.

Consistent Naming Conventions

I establish and adhere to consistent naming conventions for Tosca modules, test cases, and other
assets. This ensures that the test suite is easy to navigate, understand, and maintain, even as it
grows in complexity.

Comprehensive Documentation

I meticulously document the purpose, steps, and expected results of each Tosca test case. This
documentation is stored alongside the test cases, making it easy for other team members to
comprehend and maintain the test suite.

Continuous Improvement

I regularly review the Tosca test suite and identify opportunities for improvement. This may involve
refactoring test cases, updating modules, or introducing new reusable components. By continuously
optimising the test suite, I ensure its long-term maintainability and adaptability to changing
requirements.

Collaboration with Stakeholders

I actively collaborate with developers, product owners, and other stakeholders to align the Tosca test
suite with the application’s evolving needs. This helps me anticipate changes and proactively update
the test cases, ensuring they remain relevant and effective.

By implementing these strategies, I have been able to create a Tosca test automation framework
that is highly reusable, maintainable, and adaptable to the changing needs of the application under
test.

5) How do you collaborate with developers and other stakeholders when using Tosca?
Effective collaboration with developers and other stakeholders is crucial when using Tosca for test
automation. Here’s how I approach this:
Alignment on Application Requirements

I start by thoroughly understanding the application’s requirements, user stories, and acceptance
criteria. I collaborate with the product owner, business analysts, and developers to ensure that the
Tosca test suite aligns with the application’s intended functionality.

Shared Understanding of Test Automation Approach

I work closely with the development team to establish a shared understanding of the test automation
approach using Tosca. This includes discussing the test case design, data-driven testing strategies,
and the integration of Tosca with the CI/CD pipeline.

Continuous Communication and Feedback

Throughout the test automation process, I maintain open communication with the development team.
I provide regular updates on the test execution results, identify any issues or defects, and collaborate
to resolve them in a timely manner.

Defect Tracking and Reporting

Tosca’s integration with defect tracking systems, such as Jira, allows me to seamlessly log and
manage bugs identified during test execution. I work with the development team to ensure that
defects are properly documented, prioritised, and resolved.

Knowledge Sharing and Training

I actively share my knowledge and expertise on Tosca with the development team. This includes
providing training sessions, conducting workshops, and creating documentation to help the team
understand the tool’s capabilities and how to effectively leverage it.

Collaborative Test Case Design

In some cases, I involve the development team in the design of Tosca test cases, especially for
complex scenarios or areas where their domain expertise is valuable. This collaborative approach
helps ensure that the test cases are comprehensive and aligned with the application’s
implementation.

Continuous Improvement and Feedback Loop

I encourage open feedback and continuous improvement of the Tosca test automation framework. I
regularly solicit input from the development team and other stakeholders to identify areas for
improvement, optimise test case design, and enhance the overall testing process.
By fostering strong collaboration and communication with the development team and other
stakeholders, I am able to effectively leverage Tosca to deliver high-quality test automation solutions
that meet the needs of the application and the organisation.

Conclusion
Job seekers now have the upper hand with this Tosca interview guide. They know the questions and
have the answers. This knowledge helps them feel less nervous and more confident.

A mock interview with iScalePro makes them even better. They can practise their answers and get
feedback. With this preparation, they are more likely to get the job.

So, don’t just read this article. Use it and iScalePro to get your dream Tosca job. Good luck!
 Tosca Interview Questions and Answers for Beginners
1. What is Tosca Testsuite?

Ans: Tosca Testsuite, built by Tricentis Technology and Consulting GmbH, is an advanced testing
tool primarily developed using C#, with Java and VB6 also contributing to its creation. It is
extensively used for end-to-end functional and regression testing of software products. Many
notable firms, such as Toyota, Starbucks, Allianz, BMW, and Whole Foods, have adopted this
software.
2. What is the use of Tosca Qc/Alm integration?

Ans: TCShell, an integral part of Tosca Commander, offers command-line control. It operates in
two modes: Interactive mode, providing a user-friendly GUI, and Script mode, where users execute
pre-written command scripts with limited control.
Take your career to the next level in Tosca with HKR. Join Tosca Training Hyderabad now.
3. What is TCShell?

Ans: TCShell, an integral part of Tosca Commander, offers command-line control. It operates in
two modes: Interactive mode, which provides a user-friendly GUI, and Script mode, which allows
users to execute pre-written command scripts with limited control.
4. What are the loops available in Tosca?

Ans: Tosca offers two loops: Incremental Loops, executed a preset number of times, and Dynamic
Loops, which run until a specific condition is met, akin to do-while or while loops.
5. What are the advantages of Tosca Testsuite?

Ans: Tosca Testsuite's benefits include intuitive drag-and-drop functionality, scriptless and model-
based automation, a user-friendly GUI, asset reusability, and notably reduced regression testing
time.
6. What is the methodology that the Tosca tool is based on?

Ans: Tosca is a leading automation testing tool based on a model-based test automation
approach. It helps complete functional testing and allows software testers to perform tests more
quickly.
7. What are the components of the Tosca Testsuite package?

Ans: The Tosca Testsuite package comprises four main components: Tosca Commander (akin to
an IDE), Tosca Executor (for test execution), Tosca XScan (for scanning input fields), and the Test
Repository (for workspace storage).
8. What types of testing can be done with Tosca?

Ans: Tosca supports various testing types, including GUI testing, mobile testing, API testing, BI
and data warehouse testing, and exploratory testing.
9. What is Tosca CI?

Ans: Tosca CI enables automated test case execution directly from a build server. The CI client
runs tests and reports results in XML format to the build server. The popular CI tools for continuous
testing are Jenkins, Travis CI, Bamboo, etc.
10. What is synchronization in Tosca?

Ans: Synchronization in Tosca aligns automated test case execution with application speed using
processes and events. Here, the “WaitOn” ActionMode manages the process efficiently.
11. What is Exploratory Testing?

Ans: Exploratory testing in Tosca is a dynamic approach combining learning, test design,
execution, and result interpretation. It is classified under the Execution Section in Tosca
Commander.
12. What is a recovery scenario in Tosca?

Ans: A recovery scenario in Tosca outlines steps for the tool to follow in unexpected situations. It
also ensures continued test execution or relevant handling of test failures.
13. What is a template in Tosca?

Ans: Templates in Tosca are structured models for creating reusable, consistent test cases. They
are particularly beneficial for tests with similar step sequences.
14. What are the types of errors in Tosca?

Ans: Tosca identifies three error types: Verification failure (unmet expected results), dialogue
failure (application errors), and User Abort (manual test termination).
15. What is Test Data Management?

Ans: TDM refers to managing the data required for the Test Cases. When creating a workspace,
Tosca automatically connects to the common repository where the test data resides. We can
connect to another test data source and manually change the connection string to a different
storage.
16. Can Tosca be integrated with Jira?
 Ans: Yes, integration of Tosca with Jira is feasible and beneficial. It mainly uses the Tasktop
Integration Hub within Tosca Connect. This link fosters improved collaboration between
development and testing teams by coexisting failed tests in Tosca with defects logged in Jira.

Tosca Interview Questions for Experienced

17. What are the Tosca stages after the execution of a test?

Ans. Tosca will have to go through the following four stages after test execution.
 Pass.
 Fail.

 Error.

 No result

18. What happens if the recovery scenario fails?

Ans: If a recovery scenario in Tosca fails, the tool soars to the next higher-level recovery scenario.
If all scenarios fail, the test case is marked as failed.
19. What is the use of Rescan?

Ans: Tosca's Rescan feature enables you to reconsider already scanned modules, which will
benefit when UI updates occur.

20. Define business parameters in Tosca.

Ans: In Tosca, business parameters are customizable values for test cases, including XML
elements, headers, JSON data, settings, and response details. These can be manually set within
modules and are adjustable if payloads change.

21. Explain the Tosca Query Language.

Ans: Tosca Query Language or TQL is vital to crafting complex search queries in Tosca. It
elegantly drives through a project's landscape, focusing on objects, their relationships, and
attributes. The nuanced nature of TQL, being context-sensitive, allows for a customized approach
to querying within Tosca's environment.
22. Can we perform Excel operations in Tosca?

Ans: Tosca excels in collaborating with Excel, allowing seamless operations. It utilizes specific
Excel modules that must be imported into the workspace. Installing MS Excel 2003 or 2007 is
essential for optimal functionality. It showcases Tosca's compatibility with Microsoft's software.
 23. How can we fetch test data from Excel using Tosca?

Ans: Tosca offers dual methods for importing test data from Excel. For single TestCase scenarios,
TemplateInstance is used. It effectively produces the required number of test cases from Excel
datasets. For cases involving various TestCases and external data sources, the Excel Engine
module or custom VB scripts can import Excel data efficiently.
24. How can we identify objects in the Tosca Testsuite?

Ans: In the Tosca Testsuite, finding an object is a key to test automation. The suite offers four
distinct methods for object finding:
 Finding by properties, where objects are recognized based on their inherent attributes.
 Finding by the anchor involves using a stable neighboring object as a reference point.

 Identifying by image, where objects are identified through visual recognition.

 Identification by index, which relies on the object's position within a list or a collection.

25. How can we use multiple browsers in the same test case in Tosca?

Ans: We cannot trigger different browsers in Tosca. However, we can perform cross-browser
execution. We can use buffers to automate a TestCase with an app running on other browsers.
Using buffers, we can change the value in the test configuration parameter at runtime. By using the
TBox Set Buffer, we specify which browser needs to be used for each buffer.g
26. How can we run ExecutionLists?

Ans: ExecutionLists in Tosca can be launched. Users can simply select the 'Run' option from the
context menu in Tosca Commander or utilize the F6 key as a shortcut for execution in the
Execution section. Further, you can choose the ExecutionLists of your choice through Ctrl + left
mouse button to execute more than a list.
27. How can we run tests in ScratchBook?

Ans: Tosca's ScratchBook feature offers flexibility in test execution. It allows users to perform trial
runs on TestCases with options such as running objects immediately upon creation or arranging
and executing them in a specific order through drag-and-drop functionality.
28. What is the difference between ExceutionLists and ScratchBook?
Ans: ExecutionLists in Tosca serve to gather and execute a set of completed TestCases at a time.
On the other hand, ScratchBook is designed to run individual TestCases. It is handy for testing
newly created or incomplete TestCases.

29. Can we perform a PDF comparison using Tosca?

Ans: Tosca supports PDF comparisons through the TC PDF Compare tool, which is available on
the Tosca Exchange Portal. This tool allows users to compare two PDF files. It highlights
differences in the ExecutionLog post-execution.
30. Can we create TestCase templates manually?

Ans: Using the Tosca BI modules, Creating TestCase templates manually is possible in Tosca.
Users can produce templates by right-clicking on a test case and selecting the “Convert to
Template” option from the context menu.
31. What is the need for the test configuration parameter?

Ans: Test configuration parameters in Tosca are essential for setting object values. They simplify
test maintenance, reduce repetitive tasks, and enhance the test automation process's efficiency.
32. How can we perform API testing?

Ans: API testing in Tosca is conducted using the Tosca API Scan. This tool allows for the
complete scanning of API definitions and functions. It also enables end-to-end testing that verifies
an API's performance and error handling features.
33. How does Tosca Testsuite support Risk-Based and Model-Based Testing?

Ans: Tosca Testsuite's support for Model-Based and Risk-Based Testing is evident in its ability to
describe test cases through application scans. The suite's automation model decouples test logic
from the automation logic. It facilitates automated and manual test cases with precise input and
verification data.
34. How can you check within Tosca whether a file exists in a specific directory?

Ans: Tosca includes a "TBox File Existence" function, allowing users to verify the presence of a
file in a specified directory. This feature contains attributes like the directory path and the file name
and supports action modes like Verify or WaitOn
35. What is TOSCA Commander?

Ans: Tosca Commander is the central user interface of the Tosca Testsuite, which is integral for
designing, running, maintaining, and analyzing test cases. It encloses various sections like
Requirement, Test Case, Modules, Execution, Reporting, and Test Script Design. All these make it
a cornerstone of the Tosca Test suite.
 36. What are the various post-execution statuses in Tosca?

Ans: Post-execution, Tosca classifies test results into:

 No result
 Error

 Passed and

 Failed.

37. What are the advantages of linking Tosca test cases with the requirements?

Ans: Linking test cases with requirements ensures:

 Testing aligns with specific needs.
 Overview of high-level requirement coverage for test analysis.

38. What are the benefits of the specifications connected to the Tosca test cases?

Ans: Linking specifications with test cases in Tosca provides:

 A method to track requirement coverages.
 A complete view of demand coverage for efficient test analysis.

39. Define the TOSCA ScratchBook limitations.

Ans: The ScratchBook, used for temporary execution logs during test development, has
limitations:
Repeated execution of a test step's action may lead to loss of details.
Execution logs may not always be accessible.
40. What do you mean by String Operations?

Ans: String operations in Tosca, typically involving regular expressions, include:

 Counting specific characters or words.
 Aligning words and verifying numeric structures.

Note: The AidPack module is required for string operations.

41. Why does Tricentis TOSCA require ScratchBook?

Ans: ScratchBook is essential in Tosca for:

 Conducting trial runs of new or improved test cases.
 Temporarily logging execution outcomes.

 Ability to run complete or partial test cases.

 42. In Tricentis Tosca, Describe the organizational units of testing procedures.

Ans: In Tosca, the automated testing includes the following organizational units:

Specification

Planning

Logging

Execution

Analysis

43. What is Tosca WebAccess?

Ans: Tosca WebAccess is:

 A web interface for workspace access via browsers.
 Independent of Tricentis Tosca Commander installation.

 Allows accessing workspace data stored on the Workspace server via a client browser.

44. How can Tosca Connect be integrated with HP ALM?

Ans: Integration steps include:

 Installing the Rest API.
 Using Tasktop with a license.

 Accompanying Tosca test scripts with HP ALM's Test Plan and Test Lab modules.

 Ensuring recent Execution logs in Tosca are accessible in ALM Testlab.

45. How many different kinds of logs are there in Tosca?

Ans: Tosca provides two types of logs:

 ActualLog: Maintains the latest and most recent execution results.
 ExecutionLog: It is produced when archiving the execution log is enabled.

46. What do you mean by BDD in TOSCA?

Ans: BDD in Tosca stands for Behavior-Driven Development, a software development technique
derived from agile methods. It produces workable documentation describing behavior and actions
in text, which is used as executable documentation.
47. List the default object components in TOSCA.

Ans. Default objects in Tosca are found in the [Link] file, include:

Standard modules like TBox XEngines and Automation Tools.

Virtual folders.

Standard Reports.

48. What does an ActionMode Constraint do?

Ans. The ActionMode `Constraint '' in Tosca helps search specific values, such as locating a
particular value in a table column
49. What do you mean by Frequency class?

Ans: The Frequency class in Tosca calculates event damage values based on frequency and
quantity, ranging from 0 to 10.
50. What do you mean by TOSCA Classic Engine?

Ans: The Classic Engine in TOSCA orchestrates test execution, leveraging a structure where test
cases are constructed as business-focused objects. This engine processes these objects and
connects them with test scripts through specific steering activities.
51. What do you mean by Damage class?

Ans: The Damage class in Tosca calculates the damage values for events, ranging from 0 to 10,
based on cost.
52. What is a Distributed Execution in TOSCA?

Ans: Distributed Execution in TOSCA involves executing many test scripts across different
devices. It is achieved by setting up TestEvents in Tosca Commander, which enables efficient and
scalable testing.

Tosca Interview Questions and Answers - Advanced

53. What purpose do TestMandates serve?

Ans: TestMandates in TOSCA are designed to execute test batches at preset times. It's crucial for
domain-specific projects in sectors like banking and insurance. They enable parallel execution of
different execution list elements without impeding the primary list
54. What is TOSCA, and what are its primary features and benefits?

Ans: TOSCA, standing for Test Automation Suite for Continuous Testing, offers end-to-end testing
solutions. Key features include model-based test automation, seamless integration, and efficient
data management. Benefits include speedy test creation, enhanced reusability, and optimal
support in Agile and DevOps.
55. Explain the difference between manual testing and automated testing. How does TOSCA
facilitate automation?

Ans: Manual testing involves direct human involvement, while automated testing uses tools and
scripts. TOSCA streamlines automation with its model-based approach. It reduces the need for
complex coding and focuses on efficient test design and maintenance.
56. How do you create a test case in TOSCA? Explain in brief.

Ans: Creating a test case in TOSCA involves launching TOSCA Commander, modeling test steps
using its graphical interface, defining test data, and executing the test case with TOSCA Executor.
57. What is the significance of modules in TOSCA, and how do you use them effectively?

Ans: Modules in TOSCA summarize test steps for reuse, enhancing efficiency and maintainability.
Effective use involves locating repetitive actions, creating modules, and integrating them across
multiple test cases.
58. How does TOSCA support data-driven testing, and why is it important?

Ans: TOSCA facilitates data-driven testing by allowing parameterization of test data and creating
versatile test cases with varying inputs. It increases scenario coverage and reduces redundancy. It
uses the TCD (test case design) approach.
59. What are TOSCA Execution Lists, and how do they help in test execution?

Ans: Execution Lists in TOSCA are grouped test cases for organized and efficient execution,
allowing for classification based on criteria like priority or functionality.

60. Discuss the concept of test automation frameworks. Have you worked with any specific
frameworks in TOSCA?

Ans: In TOSCA, test automation frameworks provide structured guidelines for test design and
execution. My experience includes working with TOSCA's data-driven frameworks and enhancing
test reusability and maintainability.
61. How do you handle dynamic elements or elements with changing properties in TOSCA
scripts?

Ans: Managing dynamic elements in TOSCA involves effectively assisting dynamic behaviors with
stable identifiers, regular expressions, and waiting for statements.
62. Can you explain the concept of Test Case Design?

Ans: Test Case Design in TOSCA involves crafting test scenarios, steps, and expected outcomes
to form the foundation of automated testing. This approach ensures clarity in objectives and
enhances test coverage.
63. What is the role of Test Configuration and Test Data Management in TOSCA?

Ans: Test Configuration in TOSCA involves setting up test environments, while Test Data
Management (TDM) handles data provisioning. Both are essential for executing tests under
controlled, repeatable conditions.
64. Describe the process of integrating TOSCA with version control systems like Git.

Ans: Integration involves setting up a Git repository for TOSCA projects, configuring TOSCA to
work with Git, utilizing TOSCA's version control features, and managing project versions
collectively.
65. Have you used TOSCA's Continuous Integration and Continuous Testing (CI/CT) capabilities?
If so, how?

Ans: I have integrated TOSCA with CI/CT pipelines, using tools like Jenkins to automate testing as
part of development. It ensures continuous testing and early issue identification.
66. How do you handle exception handling and error reporting in TOSCA test scripts?

Ans: In TOSCA, exception handling involves managing errors using conditional statements and
error blocks, with built-in reporting features for detailed analysis.
67. Discuss the advantages and disadvantages of using TOSCA for cross-browser testing.

Ans: TOSCA excels in code reusability and browser-independent test design for cross-browser
testing. However, compared to specialized tools, it may require additional configuration for
complex scenarios.
68. What is TOSCA's approach to handling mobile application testing? Have you used it for
mobile automation?

Ans: TOSCA's Mobile Engine facilitates mobile app testing on Android and iOS. My experience
with mobile automation in TOSCA involves creating test cases and utilizing the mobile engine to
test devices or emulators.
69. How do you generate reports and analyze test results in TOSCA?

Ans: TOSCA offers customized reporting and analytics for test execution, including integration with
third-party tools for advanced analysis.
70. Explain the concept of reusable test assets and their significance in TOSCA.

Ans: Reusable test assets in TOSCA, like test cases and modules, greatly promote efficiency and
consistency and reduce effort in test case creation and maintenance.
71. Have you worked with TOSCA's API testing capabilities? If yes, describe your experience.

Ans: My experience with TOSCA's API testing includes creating test cases for RESTful and SOAP
APIs, defining API endpoints, and managing request parameters and expected responses.
72. How do you handle Test Data Management and parameterization in TOSCA?

Ans: In TOSCA, TDM includes creating data sets separate from test cases and parameterizing
them for reuse. The TDM module facilitates this process, enhancing test coverage.
73. Can we run a template in the Scratchbook?

Ans: Running templates directly in the Scratchbook may not be a default feature in TOSCA.
Instead, templates are typically executed via Test Configurations in TOSCA Commander.
74. What options are available if you want to run a test in the Scratchbook?

Ans: In TOSCA's Scratchbook, tests can be run using the "Execute" option for the current test
case, the "Debug" option for step-by-step analysis, or "Run Configuration" for running with specific
settings.
Take your career to the next level in Tosca with HKR. Join Tosca Training now.
75. Will recovery scenarios work in the Scratchbook?

Ans: TOSCA's Scratchbook is mainly intended for quickly creating and debugging tests, with
recovery scenarios managed in test suites or through the TOSCA Commander interface.

76. Differentiate between Tosca and Selenium.

The following are the key differences between Tosca and Selenium:
 Tosca is a leading automation tool for testing, with licensed and paid versions. Selenium is a
free and open-source automation tool for app testing.
 Tosca has integrated reporting features, but Selenium has no in-built reporting features.
 The Selenium tool requires scripting in different languages, such as Java, Python, etc. But
Tosca doesn’t require any scripting or coding as it is very easy to use.

 Tosca supports test data management, but Selenium doesn’t support this feature.

 Tosca supports testing APIs, whereas Selenium doesn’t support API testing.

77. Define Instantiation in Tosca.

Ans. In Tosca, instantiation is a process to create instance test cases. These test cases are
template-based and defined under the section test case design. This process is also called data-
driven testing.
78. Nam the various looping statements in Tosca.

Ans. Tosca supports the following looping statements: IF, DO, & WHILE to execute TestSteps with
different sections.
79. Explain about DokuSnapper in Tosca.

Ans. In Tosca, DokuSnapper is a function that creates MS Word documents. These documents
include all the data related to the executed test steps. The document’s name consists of the
execution timestamp and the script name. To allow DokuSnapper to configure options, go through
the steps below: Settings > Settings Dialog > Settings Engine > Settings DokuSnapper.
Conclusion