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.
Now let's have a look into the tosca interview questions for beginners and experienced in detail.
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
TC-Shell is the command-line control of the Tosca Commander. It can be started in two ways,
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.
There are 2 types of loops available in Tosca,
The advantages of Tosca Testsuite are,
Ans: Tosca is based on LinearQ(m) methodology
Business parameters allow you to set the values you want in your test cases.
The below can be specified manually within the module:
Business parameters can also be revised if the payload has changed.
Tosca Testsuite package contains four components,
Using Tosca, we can perform GUI testing, mobile testing, API testing, BI and data warehouse testing, exploratory testing, etc.
Take your career to next level in Tosca with HKR.Join Tosca Online Training now.
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:Synchronization in Tosca allows the execution of automated TestCases to be synchronized by using processes and events so it can match the application speed.
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.
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.
Tosca has three different types of errors,
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.
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.
If you want to Explore more about Tosca? then read our updated article - Tosca Tutorial.
We can fetch test data from Excel in two ways,
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.
There are 4 ways to identify objects in Tosca,
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.
ScratchBook allows us to perform trail runs on TestCases. We have the following options to run tests in a ScratchBook,
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.
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: 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
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.
If you have any doubts on Tosca, then get them clarified from Tosca Industry experts on our Tosca Community!
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:Tosca describes the test cases by scanning the application. The automation model contains the logic of automation for the decoupling of the test logic as defined in the test case. If the appropriate models have been established, they can be used to perform both automated and manual test cases with input and verification data.
Ans: Test configuration parameters can help you customise your tests to set values. It can also be used for the use of Tosca objects. For the following Tricentis Tosca objects, you can build test configuration parameters:
Ans:Tosca offers us with a standard PDF comparison module. This feature supports two PDF files to be automatically linked to each other. If any variations are detected, they will be shown in the ExecutionLog after the test is run.
Ans:By using "TBox File Existence," we can verify whether or not a file exists in a particular directory. Contains the following attributes:
Directory: The directory to the file to be searched.
File: Name of the file to be reviewed. You may use Verify or WaitOn ActionModes.
Batch starts on 10th Mar 2021, Weekday batch
Batch starts on 14th Mar 2021, Weekend batch
Batch starts on 18th Mar 2021, Weekday batch