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

---

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

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 Tosca Query Language (TQL), Module Section, Tbox framework, and Classic engine. 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 4 are technical. Go ahead and enjoy reading…

Tosca Interview Questions – Part 4 (TQL, Module Section, TBOX and Classic engine)

---

1. Name some important components which are part of TBOX in TOSCA?

 

Ans. Following are the components:

1. Tosca XScan
2. Tosca XML Engine
3. Tosca XBrowser Engine
4. Tosca Webservice, JSON Engine
5. Tosca Mobile+ Engine.

 

---

2. What are the types of search available on the objects in TOSCA commander?

 

Ans. Tosca commander provides or facilitates any objects to be searched by using 2 different search options:

1. Simple Search
2. TQL (TOSCA Query Language) Search.

 

---

3. What is TQL or TOSCA Query Language?

 

Ans. Just like normal search is available on objects present in the project, a different approach called TQL search is also present which is advanced in nature and provides faster and accurate results to work upon. This option enables searching all the objects, its relations and properties within a project. We can select or configure the properties or relation in the search window. For example, we can search all TestCases that are not assigned to any ExecutionLists.

 

---

4. Explain the formal structure of TOSCA Query Language?

 

Ans. Since the TQL is formal language for querying the objects, it has its own structure. This structure consists of terminals and non-terminals.

Terminals represent exactly the atomic elements, for example “]”,”:” etc.  And they cannot be replaced by any other statement or expression. Usually they are special character or they start with Uppercase.

On the other hand, Non-terminals are exactly the short syntactical statements or so called expressions. These can be replaced by any other expressions. The other expression replacing the Non-terminal can be Non-terminals or Terminals type. Usually these start with lowercase.

 

---

5. Can you give some light on the EBNF notation used in TOSCA Query Language?

 

Ans. We all know what exactly EBNF notation (for those who don’t know can imagine or visualize it as syntax for writing something) is but what is being followed in TQL is described below:

1. For logical operations use pipe ” | “ for example, b | c.
2. For describing an option use “[…]”,
3. For group expressions or statements use “(…)”. Point to be noted here is that the content must be used exactly once.
4. For an iteration on some expression or using an expression use “{…}”.
5. When you want your statement or complete expression to be considered word-by-word use ‘…’.

 

---

6. Briefly describe the syntax of a TQL Search in TOSCA?

 

Ans. The TQL search syntax has three components,

1. arrowOperator >>  (=> or ->)
2. returnToken >> (:), and lastly
3. search expression

Complete syntax can be visualize as

YourQuery := {arrowOperator [returnToken] searchExpression}

 

---

7.  Will my search at TestFolder or Module or RequirementFolder or Project Folder results in similar outcome or different? OR What is context-dependent TQL Search?

 

Ans. If you are choosing some folder at random then keep in mind the starting point in your TQL search has an effect on the search to be carried out.

This results in different results because your context got changed with change in selection of starting point. You can visualize it as a Tree structure wherever you begin your search, below it your TQL will be carried out. And hence searching performed on a project root element produces different results from one based on the Module folder, etc.

 

---

8. Can we perform recursive search using TQL? OR How do you perform Simple and recursive TQL Searches in TOSCA?

 

Ans. The answer to this question lies in the scenario in question. If you want to do simple search we can do so using the single arrow symbol indicating a simple operation like

“->”,

whereas for queries to be considered in recursion we start with the “equal with arrow” symbol like

“=>“

indicating recursive operation.

 

---

9. What are subparts and Superparts? OR What is the difference between subparts and superparts in TQL?.

 

Ans. For an expression to be evaluated properly in TQL, a concept of subpart and superpart had been introduced. The Subparts searches for all child elements in TOSCA whereas superparts searches for parent elements.

For example:

The expression “->SUBPARTS” returns the sub elements as a result.

The expression “=>SUBPARTS” includes the sub elements within the sub elements (its recursive).

The expression “->SUPERPARTS” returns the super elements as a result.

 

---

10. Can you define what exactly is the Base Engine in Tosca? OR what is Classic Engine?

 

Ans. Base Engine is used for executing each of the automated TestCases. The Base engine follows an architecture according to which the test cases are managed as business-based objects. The Base Engine receives the business-based object information about the test case and activates the steering of the test object in SUT. The steering is performed by the corresponding engines which understand and formulate the technology in question.

 

---

11. Can you name some Classic engines or Base Engines in TOSCA?

 

Ans. There are lot of names, so few of them I’m sharing below:

1. Console Engine,
2. Database Engine,
3. Delphi Engine,
4. DotNet Engine,
5. Excel Engine,
6. Firefox Engine,
7. Flash Engine,
8. Gupta Engine,
9. Host Engine,
10. HTML Engine,
11. Java Engine,
12. UIA Engine,
13. Manual Engine,
14. Outlook Engine,
15. Powerbuilder Engine,
16. Visual Basic Engine

 

---

12. Describe or explain Classic Engine or Base Engine object model in TOSCA?

 

Ans. The model states that for any test case to execute, it needs to provide information across 3 different layers:

1. Business information:

 

-Business based information is related to the content of the TestCase and the test data. When you trigger the execution of the test cases, an XML file is exported from Tosca Commander which is utilized in or we can say which serves as engine input and contains the business-based information.

 

1. Definition information:

 

– Definition information layer contains the description of the logical or testobject screen to be steered from the technical point of view.

 

1. Representational Layer:

 

-The objects of the representation layer allow the control elements of the test object to be accessed. The current technical values of the screen element to be steered, such as table content, field positions, etc.

 

---

13. Explain Keywords in TOSCA.

 

Ans. Keywords are the VB scripts that allows individual steering requirements to be conveniently integrated into an engine. Some of the keywords enable the steering of UI screens as well. These keyword VB script files are executed by the engine upon test execution.

 

Keywords are used in the Modules section in TOSCA Commander.

---

14. From technical point of view, which components are part of Base Engine in TOSCA?

 

Ans. TOSCA Base Engine contains all the basic objects for processing automated test cases.

Following are the components which Base engine has:

 

A. Engine.dll:

 

Engine.dll is basically a COM.dll, that comprises or in technical terms “encapsulates” the required classes. This dll uses a set of basic objects like services.dll, etc.

 

B. Executor.exe:

 

Executor.exe is an executable file. This file is responsible for test execution and it also uses Engine.dll for execution.

 

C. ToscaWizard.exe:

 

ToscaWizard.exe is an executable file. This file is responsible for scanning the definition data of the test object in the target SUT.

 

---

15. Does TOSCA support testing of JavaFx based applications?

 

Ans. JavaFx controls are identified as controls which cant be steered, but in case of JavaFx is embedded in Swing modules then with the help of custom controls it is possible to scan and automate same.

 

---

16. What is Tosca TBox framework?

 

Ans. There are many frameworks in Tosca which help us to work with identification of controls and TBox is one them. This framework is the basis for steering all engines for both Graphical User Interface tests and non-GUI tests for instance GUI like web and Non-GUI like API.

Another interesting point to note here is it is built on MS .NET technology. If you have worked as a .Net developer, JAVA developer, etc. then you can understand the flexibility and adaptability more than who are not from development background.

Read More here =>TBox Architecture and Interview Questions

 

---

17. What is the difference between TBox and Classic Framework? OR What are the benefits of the TBox?

 

Ans. The TBox framework has many advantages over Classic Engines which are discussed below:

1. The controls or options on GUI or Non-GUI environments are being developed on various new evolving technologies for instance say some controls are built on ajax, some are java based, some are Oracle app controls etc. To cop up with all these TBox framework provides a common interface to support all these technologies which in turn you might not find in Classic engines.
2. All your effort from modules creation to building up and executing the test cases becomes faster. In comparison to Classic ones it shows higher performance, which is really an important aspect as for ‘say in agile’ environment everything; right from modules to test cases; has to be done as fast as possible to accommodate the new changes and validate the same in much faster pace plus supporting the existing execution list in discussion.

Read More here =>.TBox Architecture and Interview Questions

 

---

18. What are the steps involved in Object Steering in TOSCA?

 

Ans. Test objects are steered in two steps.

1. object access.
2. object steering.

---

19. What is a metacharacter? Can we escape meta characters in TOSCA? If yes then How?

 

Ans. Metacharacter is a character which has some special meaning like in regular expression we have ‘?’, ‘*’, etc each having their won significance. TOSCA uses special characters for certain functions. For escaping any Special characters used as values we require a backslash, for example \+ or \d.

 

---

 20. Does TBox come with standard installation?

 

Ans. Yes TBox comes as part of the standard installation.

---

 

Below are some questions related to TBox framework and architecture:

1. Does TBox only support GUI? No, then describe which all it supports other than GUI?
2. On which technology TBox framework is built upon?
3. Can we extend the TBox framework, somehow say using some programming?
4. What all capabilities does TBox offers?
5. How is TBox Architecture designed?
6. What are the motives behind this framework? OR why is it necessary to follow such layer structure?
7. What all layers do? describe briefly.
8. What is the difference between TBox and Classic Framework?
9. What are the benefits of the TBox?
10. How TBox is improving the performance of creation and execution of Tests?
11. Which expressions can be followed throughout the TBox framework? Give some examples on it.
12. What all actions are available as part of TBox?
13. Can all Classic framework test cases be converted to TBox?
14. What all modules are available in TBox?
15. Does it require for you to import standard.tce to get all these modules?
16. What all modules you will require mostly to work with web application? Can you name some.
17. In terms of migration what points should you remember?

If you would like to follow the answers to above questions please visit

TBox Architecture and Interview Questions

 

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 1

Tosca Interview Questions – Part 2

Tosca Interview Questions – Part 3

 

---

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.