Tricentis Tosca (Topology and Orchestration Specification for Cloud Applications) is among the top testing tools available in the market right now. Over time, it has evolved as a big competitor in the field of automation tools. So landing a job as a Tosca expert will guarantee you a promising career. In this post, we will be discussing the top 30 Tosca Testsuite tool’s interview questions for those who are aiming to grab a good job opportunity. These questions are gathered after conferring with professionals and after analyzing data collected from several interviews held for the Tosca job position. Make sure to take a look at the below frequently asked questions and answers to gain confidence before you attend an interview (or) just go through them to enhance your learning curve.
Ans: Tosca Testsuite is a testing tool developed by Tricentis Technology along with Consulting GmbH. C# is the main language used to build the tool. Java and VB6 are also used in the creation of this tool. It is used for carrying out end-to-end functional and regression testing on software products. Major companies like Allianz, Toyota, Starbucks, BMW, HBO, Whole Foods, etc are using this tool
The advantages of Tosca Testsuite are,
Ans: Tosca is based on LinearQ(m) methodology
Tosca Testsuite package contains four components,
Ans: Using Tosca, we can perform GUI testing, mobile testing, API testing, BI and data warehouse testing, exploratory testing, etc.
Ans: Tosca has three different types of errors,
Ans: There are 4 ways to identify objects in Tosca,
Ans: We can run an ExecutionList by clicking on the Run option in the context menu of the Tosca Commander. We can also run it by directly pressing on the F6 key in the Execution section.
Ans: ScratchBook allows us to perform trail runs on TestCases. We have the following options to run tests in a ScratchBook,
Take your career to next level in Tosca with HKR.Join Tosca Online Training now.
Ans: ExecutionLists are used to accumulate completed TestCases and run them at once. Whereas a ScratchBook is used for running individual TestCases upon creation of TestCases or to check TestCases that are still in an incomplete state.
Ans: Test Data Management is the process of managing data required to carry out the TestCases. When a workspace is created, Tosca automatically establishes a connection to the common repository where the test data resides. We can even connect to another test data source, we can manually change the connection string to a different repository.
Ans: Tosca Query Language (TQL) is used to write search queries for searching through objects, object relations, and object properties within a project. TQL is context-dependent.
Ans: Yes, we can. Tosca provides standard Excel modules that we have to import to our workspace. We should also have Microsoft Excel 2003 or Microsoft Excel 2007 installed on our system for it to work.
Ans: We can fetch test data from Excel in two ways,
Ans: We cannot trigger multiple browsers in Tosca. However, we can perform cross-browser execution. When we need to automate a TestCase with an application that has to run on different browsers, then we can use buffers. Using buffers, we can change the value in the test configuration parameter at run-time. And then specify which browser needs to be used for each buffer using the TBox Set Buffer.
Ans: TC-Shell is the command-line control of the Tosca Commander. It can be started in two ways,
Ans: Yes, we can integrate Tosca and Jira using Tasktop Integration Hub in Tosca Connect. To improve collaboration between development and the testing team, Tosca has provided Jira integration. We can synchronize failed tests in Tosca to defects in Jira.
Ans: HP Quality Center tool can be integrated with Tosca so that users can create, save and update Tosca test cases directly in ALM. The test execution results will also be made visible in HP ALM.
Ans: There are 2 types of loops available in Tosca,
Ans: Yes, the TC PDF Compare from Tosca Exchange Portal can be used for comparing pdf files. We can give 2 pdf files to be compared to this. The differences found will be shown in the ExecutionLog once the execution is completed
If you want to Explore more about Tosca? then read our updated article - Tosca Tutorial.
Ans: Tosca Continuous Integration allows executing test cases directly from the build server without the user having to manually execute them. The Tosca CI client runs the test cases and sends the test results to the build server as an XML file.
Ans: Recovery scenario is for the tool to react in an unexpected situation i.e a collection of test steps that need to be executed in case a particular test fails.
Ans: If a recovery scenario fails, Tosca moves on to the next higher level recovery scenario. If all of the recovery scenarios are failed, Tosca reports the test case as failed.
Ans: Tosca Recan is used for scanning the already scanned module. When you have a scanned webpage in a test case and if the UI is updated a bit, then we need to rescan the webpage and add it to the test case.
Ans: A Tosca template is a model (or) a structured format that can be reusable for creating concrete TestCases. The TestCases that have a similar sequence of steps can be converted to templates.
Ans: Yes, we can create a TestCase template manually by using the Tosca BI modules. To create a template, right-click on the test case and select the “Convert to Template” option in the context menu.
Ans: The test configuration parameter is used to set values for objects. To simplify the maintenance of tests and avoid repetitions, we can set the values to test configuration parameters
We can perform API testing using Tosca API Scan. With this, we can scan API definitions and functions of an API. Tosca API Scan can be used to perform end-to-end testing to verify the performance and error-handling of an API.
Ans: Synchronization in Tosca allows the execution of automated TestCases to be synchronized by using processes and events so it can match the application speed.
If you have any doubts on Tosca, then get them clarified from Tosca Industry experts on our Tosca Community!
Ans: Exploratory testing is the process of learning about the product, designing and executing tests, interpreting test results all at the same time. It is called a plan-as-you-test approach. It is available under Execution Section in the Tosca Commander.