Latest Tosca Interview Questions and Answers (Latest Interview Questions) – Part 1

---

Welcome to this post! -“Tosca Interview Questions and Answers (Latest Tosca Interview Questions) – Part 1”.

If you are looking for latest Tosca interview Questions, then you are at right place. This posts consists of some exhaustive questions which had been part of interviews. These questions covers various topics such as introduction to Tosca, model based technique, commander, TCShell, etc. These questions will give you extra knowledge over the subject as well as various perspective on how the questions have been asked. Most of the questions in this Tosca interview questions part 1 are general questions. Usually these are assumed to be known before moving to deeper technical questions on Tosca, Go ahead and enjoy reading…

Tosca Interview Questions : General Questions:

---

1.   What is Tricentis Tosca?

 

Ans. This tool allows users to create automated and functional test cases around the system under test (SUT).

 

---

2.   What are the Advantages of using TOSCA?

Ans. Following are the advantages:

1. It follows model-based automation.
2. It reduces your coding to minimum
3. It has various clear and crisp sections so that it can supports you well enough in proper Test Management like check-in/check-out, distribution of modules, testcases etc,
4. It can be integrated to a number of tools which are used in CI/CD activities like Jenkins, etc.
5. It allows you to recognize and do action on previously unidentified controls using your own written custom control’s modules.
6. It supports a lot of applications; doesn’t matter windows, web apps, CRM apps, etc. It allows also BI testing solutions, Analytics solutions with their additional extensions.

 

---

3.   What are the main components of Tosca?

Ans. Below listed are main components:

• Tosca Commander,
• Tosca Executor,
• Tosca Wizard,
• Test Repository.

 

---

4.   What is the Current Version of TOSCA?

 

Ans. The latest version of TOSCA Test suite is 11.2 (it might change till the time you are reading).

---

 

5.   What all extensions are available which user can purchase?

 

Ans. There are extension such as listed below:

• Tosca Analytics
• Tosca BI
• Tosca Connect
• Tosca Continuous Integration
• Tosca Distributed Execution
• Tosca Orchestrated Service Virtualization
• Tosca SAP Solution Manager Integration

---

6.   What is TOSCA Commander?

 

Ans. The core of TOSCA is Tosca Commander. It can be said as an IDE which facilitates user to create, manage, execute and analyze the Test Cases. It has lot of sections like Modules, Test Cases, testcase Design, Requirement, Execution Lists, Report, etc.

---

7.   What is TCShell?

 

Ans. The TC-Shell is the command-line interface of TOSCA Commander, which means you can do a lot of operations on your test objects without opening Tosca Commander. This Shell can be started in two different modes, interactive and script.  The frequent usage of it happens when you try to deploy the newest test execution package on designated folders for tools like Jenkins to target and run those.

 

---

8.   What are the limitations and functions of ScratchBook in TOSCA?

 

Ans. First of all, ScratchBook is place or section where temporary results are shown. These results can be reviewed and future amendments can be made based on that learning on the test cases. So, in short, it is our debugger window. Good point in scratchbook is that it allows you to run a step or some steps or complete testcase as per your requirement which is amazing.

Limitations are not major but self-explanatory:

It will not show detailed action being in steps if they are in repetition, mean to say, you can expand the steps but might not see the actual result. It will mark it those as passed but what exactly led to this status should be inferred intellectually.

For custom controls errors or exception users might now see appropriate messages, or sometimes nothing at all. This is all because user himself has not coded well enough to capture all failing scenario’s.

 

---

9.   Explain the content of Project root element in TOSCA?

 

Ans. The project root element acts as a place holder for all the sections, imported objects etc. It contains the sectional folders like ExecutionLists, Modules, Reporting, Requirements, TestCaseDesign, TestCases.

 

---

10.   What is Model-Based Testing(MBT) and model-based automation framework?

 

Ans. MB Technique is combination of some technical and graphical representations to visualize the test object in question. When we use such approach in testing, it is MB Testing. The use of graphical and technical representation is done by collecting all the information available with SUT, and later separate it from the actual code or script. This is the reason why this method is so efficient.

Secondly, automation framework around MBT conforms the technical (usually this is technical layer) and graphical representation (usually this is presentation layer) with steerable objects of SUT so that required actions can be performed along with the values. It is only at the point of execution that the business logic contained in the test cases is combined with the steering information (technical representation) contained in the automation framework to work upon the system under test. This leads to provide a more scalable, robust and cost-effective approach to software testing. They also provide us with better control on generated test cases and with the option to automate test design and implementation of various activities.

 

I really hope you enjoyed reading the post. If you have any doubt on this please feel free to add your comment below.

 

---

And if you like to read more on TOSCA Interview Questions please follow below links:

Tosca Interview Questions – Part 2

Tosca Interview Questions – Part 3

Tosca Interview Questions – Part 4

---

If you would like to keep track of further articles on TOSCA. I recommend you to SUBSCRIBE by Email and have new articles sent directly to your inbox.