GVPL Global

TOSCA Interview Questions

Tosca Interview Questions for Entry level

(1-24) 2-8 Page

Tosca Interview Questions for Intermediate level

(25-44) 9-14 Page

Tosca Interview Questions for Advanced level

(45-80)15-23Page
Tosca Interview Questions for Entry level
Q1) Discuss about Tricentis Tosca.

Ans. Tosca is now one of the market leader as a test automation tool which has
the ability to automate all kind of applications. It allows to design script-less
automated tests.
important features of Tosca:
1. Fast execution and capable of Continuous testing approach to support
DevOps
2. Supports module based test development which maximize the usage of
reusability.
3. Required minimum maintenance efforts.
4. Ability to integrate with major third party tools.
5. Test development is easy as it follows script less test automation.

Q2) Tell me the major components of Tosca?

Ans. The important components which are available in Tosca are –
1. Tosca Commander.
2. Tosca Executor.
3. Tosca ARA (Automation Recording Assistant)
4. Tosca Wizard
5. Test Repository.
6.
Q3) Explain the advantages of Tosca as a test automation tool?
Ans. The benefits provided by Tosca automation tool mentioned below:
1. One tool combines many features.
2. Supports script-less test automation.
3. Test management.
4. Bulk updates are possible.
5. Assets can be reused.
6. Compatible with different platforms.
7. It follows model-based testing approach.
Q4) Define TOSCA Commander?
Ans. The Tosca commander is the UI interface of the tool which allow users
to design, maintain, execute and analyze the test cases. So, it is the core
backbone of the Tosca Test suite. The Tosca commander build with different
sections such as Requirement, Modules, Test Case, Test script Design,
Execution, and Reporting, etc.
(Tosca Commander) Tosca Interview Questions and Answers

Q5) How to execute test scripts from Tosca ExecutionLists?

Ans. The different approaches of Tosca test executions are mentioned below –
1. Using the shortcut key F6, the execution can be initiated.
2. Right-click on the selected test cases and select the “Run” option.
3. Select and run the ExecutionLists.
4.
Q6) What are the different components available in TOSCA?
Ans: There are four different components available in Tosca
1. Tosca Commander
2. Tosca Executor
3. Tosca Wizard
4. Test Repository
5.
Q7) How to execute test scripts from Tosca ScratchBook?
Ans. We can perform trial run of the newly created or enhanced test cases
through the ScratchBook to check the correctness. The Tosca logs the
execution results in ScratchBook for temporary purposes. The entire or part of
test cases(i.e. test steps) can be executed through ScratchBook.
Two options are available to execute the testcases from scratch books which
are explained below –
1. Can be executed at any time.
2. We can organize the test cases in scratchbook before execution.
3.
Q8) Is it possible to integrate Tosca with Jira?
Ans: JIRA is a test management tool. By integrating with JIRA, we can
manages the bug or issues which are raised in Tosca. So, if there is any new
issues are raised in TOSCA, same will be synched to JIRA through the
interface.

Q9) Explain the benefits of Tosca integration with Jira?

Ans. The benefits of Tosca Jira integration are mentioned below –
1. Synchronizes failed tests from Tosca.
2. The bug can be raised in JIRA automatically after the execution failure
in Tosca.
3. Enables the DevOps process.
4. The cross-tool traceability can be achieved.
5.
Q10) What are the different types of errors which can occurs in Tosca?
Ans. Three types or errors can appear during Tosca execution.
1. Verification-Failure: It appears when expected and actual results are
not matched for the verification step.
2. User Abort: It appears when the execution has been stopped by the
tester.
3. Dialog-Failure: It appears due to some unhandled exceptions or steps.
Q11) Explain Tosca Testsuite?
Ans. Tosca is now one of the market leader as a test automation tool which has
the ability to automate all kind of applications. It allows to design script-less
automated tests.
important features of Tosca:
1. Fast execution and capable of Continuous testing approach to support
DevOps
2. Supports module based test development which maximize the usage of
reusability.
3. Required minimum maintenance efforts.
4. Ability to integrate with major third party tools.
5. Test development is easy as it follows script less test automation.
6.
Q12) How can you read data from Excel using Tosca?
Ans. The excel data can be read with the help of either of the below approaches
–
1. In Test Case Design approach of TOSCA, data can be read from the
external excel file with predefined format.
2. The “Excel Engine” allows to import and read from excel file.
3.
Q13) Is it possible to launch multiple browsers in TOSCA?
Ans: It is not possible to launch multiple browsers in Tosca. But it can be
achieved by following below steps –
The Test Case Parameter(TCP) with the name “Browser” need to add testcase,
root folder, or execution list level.
Using the “Browser” values as InternetExplorer, Firefox, or Chrome, the
corresponding web browsers will be launched.
Q14) How to perform data-driven testing in Tosca?
Ans: The data driven test automation is possible with the help of TCD (Test
Case Design). The test sheet of TCD represents the the template where we can
create the instances which are representing the test data for individual test
cases. Again, we can create the attributes with in test sheet that represent the
each data parameters and the data values can be created with in attribute as
instances with in it.
For data reusability, we can define classes. After creation of TCD, the test
sheets with different data sets can be mapped with template test case from
where we can generate different test cases based on the different data. The test
case creation process is known as instantiation of the template test cases.

Tosca Interview Question and Answer-TestSuite

Q15) How to launch more than one browser in Tricentis TOSCA?
Ans: Launching multiple browsers is not possible in TOSCA. But the user can
achieve cross-browser execution.
To perform cross-browser execution, users need to follow the below steps:
1. A Test Configuration Parameter “Browser” should be designed either at
TestCase or its Parent Levels.
2. Users can choose the value as InternetExplorer, Firefox, Chrome.
3. The individual browsers will trigger executions.

Q16) What are the different status available after post-execution in

Tosca?
Ans: By default, Tosca provides four different states after test execution.
Those are –
1. Passed
2. Failed
3. No result
4. Error

Q17) Explain the limitations of TOSCA ScratchBook?

Ans: The temporary execution logs are stored in ScratchBook. During the test
development, we used this option for temporary execution to check the script
correctness.
If the action within a test step is executed repeatedly, the details will not be
available. Also, the execution logs are not available permanently.
Q18) Explain the benefits of linking Tosca test cases with requirements?
Ans. The main purpose is the ensure the coverage of the testing based on the
requirements. It will provides a high level picture of requirement coverage for
test analysis.

Q19) Explain the template and process to create it?

Ans: The templates in Tosca defines a unique test flow with the help of
modules. Instead of actual data, the data parameters from the TCD are linked
with. Generally, the template is nothing but something in a conventional
format. The Technical test case can be converted to the template by right-
clicking on it. The template uses the data from TCD datasheet.

Q20) Explain the advantages of specifications which is associated with

Tosca test cases?
Ans: The specifications can be linked to test cases to track the requirement
coverages. It will provides a high level picture of requirement coverage for test
analysis.

Q21) Explain Test Data Management.

Ans. Test data management enables you to deal with the test data necessary
for test execution. The data driven test automation is possible with the help of
TCD (Test Case Design). The test sheet of TCD represents the the template
where we can create the instances which are representing the test data for
individual test cases. Again, we can create the attributes with in test sheet that
represent the each data parameters and the data values can be created with in
attribute as instances with in it.
For data reusability, we can define classes. After creation of TCD, the test
sheets with different data sets can be mapped with template test case from
where we can generate different test cases based on the different data. The test
case creation process is known as instantiation of the template test cases.

Q22) What is String Operations in Tosca?

Ans. String operations are utilized for verifying or changing the strings with
regular expressions. It features count specific character/word from the
announcement, aligning a word with another word, confirming the structure of
a number, etc. You ought to have a module AidPack downloaded and
downloaded on your endeavor to execute String operations.

Q23) Why SratchBook is required in Tricentis TOSCA?

Ans: We can perform trial run of the newly created or enhanced test cases
through the ScratchBook to check the correctness. The Tosca logs the
execution results in ScratchBook for temporary purposes. The entire or part of
test cases(i.e. test steps) can be executed through ScratchBook.

Q24) What is exploratory testing Tosca?

Ans. Exploratory is an approach to record the test scenario will navigating the
scenario manually. It records the screen shots with technical information and
generates a pdf file at the end. This document can be used for future references
and training purposes.

Tosca Interview Questions for Intermediate level

25) Describe the organizational units of the testing procedures in Tricentis
Tosca?
Ans: The automated testing in TOSCA contains below organizational units.
1. Planning.
2. Specification.
3. Execution.
4. Logging.
5. Analysis.

Q26) Describe the purpose of “Tosca Query Language”(TQL)?

Ans: The TQL is the shorter form of Tosca Query Language which is used for
advance searching purposes in Tosca. Conceptually, this is similar to SQL that
means we can searched based on the conditions.

Q27) Is it possible to compare pdf using Tricentis Tosca?

Ans. Tosca allows users with a standard module to perform a comparison of
pdf files. After the comparison of two pdf files, the mismatches will be
available in execution logs.

Q28) What is Tosca CI? How does the user execute test scripts using CI
Tool?
Ans: CI stands for continuous integration. TOSCA is able to execute the
testcases through CI tools like Jenkins, Bamboo, etc. as part of continuous
testing. With the CI features, we can integrate with CI tools easily. After the
integration, test can be triggered through third party CI tools.
Tosca Interview Questions-Tosca integration with CI tool
Q29) What are the loop-statements used in Tosca?
Ans. While we need to execute test steps repeatedly, the Tosca loop is used.
Tosca provides different loop structure such as Do, For, While loops, etc.

Q30) What do you mean by Tosca WebAccess?

Ans: The Tosca WebAccess is a web interface which allows to access the
workspace through the web browsers. The installation of Tricentis Tosca
Commander is not required to work with workspaces through the WebAccess.
The workspace server system stores the data of workspaces and using the client
browsers, we can access it.
Q31) Explain the usage of Tosca API Scan?
Ans. The API scan feature of Tosca allows to create the modules after scanning
the API for a specific system. Basically, it enables to automate and design the
API Test Cases.

Q32) What is Tosca QC / ALM Integration?

Ans: The HP Quality Center (name of the latest release is ALM) is a test
management tool which manages the test development, execution and defect
cycles. Tricentis Tosca allows to integrate with Quality Center with minimum
customization. The main purposes of the integration are to manage the test
executions and the defect managements. The execution data and the defect
details will be synched between both the tool through the integration.

Q33) Explain the Tosca test configuration parameters.

Ans. The test configuration parameters (TCPs) can be used for parametrized
the test data for configuration related activities i.e. ideally it should be used for
those parameters which will be applicable across the entire test suites. Tosca
provides some in-build TCPs which are used to change the default
configuration of the Tricentis Tosca. The user defined TCPs can be created for
the below specified objects –
1. Project root element
2. ExecutionList
3. Test Case
4. ExecutionEntry
5. ScratchBook
6. Component folder
7. Configurations folder
8. Any Subfolders available in TestCase, TestCase-Design or Execution
Sections.
9.
Q34) How to integrate Tosca Connect with HP ALM?
Ans.
1. Install Rest API.
2. Install Tasktop in the test system with the License.
3. Do test script synchronization with Test Plan Module in HP ALM from
TOSCA.
4. Synchronize the execution list with the test lab module in HP ALM from
TOSCA.
5. Sync the latest execution logs, available in Tosca ExecutionList with
testset which is available in ALM Testlab.
6.
Q35) What are the modes of TC Shell.
Ans: The TOSCA commander administrator uses TC shell, and there are two
different methods of starting TC Shell.
1. Interactive mode: The interactive mode favor by new and intermediate
users, assists the user with help and options. The complete Tosca
commander GUI functionalities can be access through the interactive
mode.
2. The script mode: This is the lite version of Tosca GUI can be visible
which involves minimum interaction. It’s used for execution of scripts
in automated mode.
3.
Q36) What is Synchronization in Tricentis Tosca?
Ans. Synchronization is a process that matches the application momentum
with automation tool momentum. The ActionMode “WaitOn” is used to handle
the synchronization in a dynamic approach. Until the satisfaction of the
condition, provided as TestStepValue for “WaitOn”, the Tosca test will wait
for a pre-configured timeout value. The synchronization setting can be altered
from the settings – “Go to settings->TBox->synchronization”.

Q37) How to check the existence of a file in Tosca?

Ans. With the help of standard module “TBox File Existence,” we can verify
the existence of any specified file. This module has below attributes –
1. Directory – The location of the test file.
2. File -Name of the test file.

Q38) How many types of logs available in Tosca?

Ans: Two types of logs are available in Tosca after the test execution. Those
are –
1. ActualLog: It keeps the latest execution results and the execution
history.
2. ExecutionLog: By selecting the option “Archive actual ExecutionLog”,
this type of logs are generated.
3.
Q39) What is BDD in TOSCA?
Ans: BDD is stand for Behavior Driven Development which follows agile
methodology grounded software development process. The process is works
as per the Test Driven Development.
BDD does not generate workable test cases but workable documentation. Here,
the actions and behavior are explained as texts. This permits them to be tested
as workable documentation. Requirements are depicted as user stories.
Q40) What is the purpose of ActionMode Constraint?
Ans. The ActionMode value “Constraint” is used to search for the specified
values. For example – we can search a specific column value in a table with
the help of “Constraint” easily.

Q41) What are the Default object components in TOSCA?

Ans. During the Tosca workspace creation window, the default objects are
either auto incorporated or need to added manually using import subset option.
The default components are kept in standard.tce file which is available in the
folder “%TRICENTIS_PROJECT%\ToscaCommander”.
The default components which are associated with the file are –
1. Standard modules – All kind of default modules available which can
be used to steer different applications, include TBox XEngines and TBox
Automation Tools.
2. Virtual folders.
3. Standard Reports.
4.
Q42) What is Damage class?
Ans: This class is used to calculate the damage values for any specific events.
This is calculated based on damages in terms of cost. The range of this values
are between 0 to 10 (min to max).

Q43) What is Frequency class?

Ans: This class is used to calculate the damage values for any specific events.
This is calculated based on damage quantity in terms of frequency. The range
of this values are between 0 to 10 (min to max).

Q44) Discuss the manual test case template creation steps in Tosca?
Ans. Users can design the TestCase templates using the anticipated sections of
Samples.tce subset and Tosca BI Modules. We need to follow below steps to
create TestCase template –
1. Create a TestCase according to the user’s requirements.
2. We can convert technical test case into template by selecting context menu
option “Convert to Template” after right-clicking on test case.
3. Drag and drop the appropriate TestSheet onto the desired TestCase
Template.
4. Assign the TestSheet attributes (data parameter) for the required
TestStepValues using XL tag.
Tosca Interview Questions for Advanced level
Q45) Explain the merits of Tricentis Tosca?
Ans: The main advantages of Tosca as a test automation tool, are specified
below –
1. Allows script-less test automation approach.
2. Easy to learn the tool with very minimum skillset.
3. Test automation can be initiated at the very early phase of testing.
4. Supports the model-based test automation framework. So, it’s not
required to spent efforts on test framework creation.
5. High scale of reusability approach can be utilized with the help of
components like Modules, Reusable TestStepBlock, TCD, etc.
6. The tool itself supports the test management and functional testing
activities.
7. ALM integration is possible.
8. Can trigger the selenium testcases from Tosca.
9. Mass update is possible with the help of TQL.
10.
Q46) Is API Testing possible with Tosca?
Ans: Yes, Tosca supports the API Testing. The API Scan is used to scan create
the modules for the corresponding APIs. Using the API modules we can send
the request and receive the response for the API call.

Q47) How to use multiple web browsers within the same test case using
Tosca?
Ans. Users want to automate a test script pass over different applications that
execute on other browsers. Using buffers, changing the Test Configuration
Parameters at execution time by the below methods.
1. Alternating the value of test ordering Parameter to {B[Browser]} or any
other Buffer Name user prefers.
2. During the execution, we can change the buffer value using “TBOX Set
Buffer” module to change the value of “Browser” test configuration parameter
according to the browser name to launch.
Q48) What is TOSCA Classic Engine?
Ans: The Classic or Base engine is responsible to the test execution. Base
engine follows the architecture of the test cases which are managed as
business-based objects. The business-based object information and activities
to steer the controls, which are related to test scripts, are accepted by the
Classic engine.

Q49) What are the steps required in Object Steering in Tosca?

Ans: There are two steps involved in Object Steering:
1. Object access.
2. Object steering.
3.
Q50) Discuss Tosca Model-Based Testing?
Ans. The models represent the unit of functionalities which are created by
scanning the application. The modules contain the technical information of the
controls to steer the test objects. Now, model-based testing explain the
approach where test cases are developed and executed based on the modules.
Basically, modules are added into test case as a test step through drag-drop
approach to complete the test cases. In the testcase, we need to provide the data
as TestStepValue and actions. No scripting is required to develop the test case.

Q51) What do you mean by Distributed Execution in TOSCA?

Ans: When any user or Test wants to execute a large set of test scripts in
multiple machines, the tester must create TestEvents in Tosca commander.

Q52) Describe Test Data Management (tdm)?

Ans: The Test data Management(TDM) components are used to managing the
test data which are required for test execution. The TDM component is
available with the standard Tosca installation. The data are stored same as
shared database repository which is used to create the workspace, through the
TDM which will be assigned to test cases during the execution. In case of
SQLite, the separate instance of database is required for TDM.

Q54) How to run Tests using ScratchBook?

Ans: We can perform trial run of the newly created or enhanced test cases
through the ScratchBook to ensure the correctness. The Tosca logs the
execution results in ScratchBook for temporary purposes. The entire or part of
test cases(i.e. test steps) can be executed in ScratchBook.
After right-clicking on one or more selected test cases, test case folders or test
steps, we can initiate the execution by selection of option from context-menu.
Q55) What is the use of TestMandates?
Ans: There are many scenarios like banking, insurance, etc. domain projects;
we required a batch to be run at a specific time. This requirement can be
fulfilled using TestMandates. The test mandate allows to execute different
parts of execution list parallelly with out locking the main execution list.

Q56) Discuss the steps to instantiate TestCases using Excel?

Ans. The process instantiating means to generate the instance test cases from
the template based on the different data which are defined in “TestCase
Design” section or in excel template.
Below are the steps to instantiate TestCases with excel:
1. The template test case is required to create instance test cases.
2. The the data sheet attributes which are defined in TCD or external excel
template, i.e. the data parameters have to be linked with template attribute with
the correct syntax.
3. Right-click on the template testcase and select the context menu option
“Create TemplateInstance” to start the process.
4. The excel sheet with predefined structure, has to be displayed in the
subsequent dialog.
5. Handle the authentication dialogue and proceed.
6. Next, click on OK button to start the process.
Q57) Describe Instantiating Template?
Ans: he process instantiating means to generate the instance test cases from
the template based on the different data which are defined in “TestCase
Design” section. This approach in Tosca, is also known as data-driven testing.

Q58) What do you mean by business parameters in Tosca?

Ans. The business parameters are use to pass the data into a Reusable
TestStepBlock as arguments. The primary purpose of the business parameters
is to parameterized the use of test data in Reusable TestStepBlock instead of
using hard coded data. It can be created after right-clicking on the selected
Reusable TestStepBlock which is created in Library folder.
Q59) Explain about TC-Shell?
Ans. TC-Shell allows to control the Tosca commander from the command line.
It can be launched in two unique manners using interactive and script.
1. A group of commands which are written in a flat file (such as bat file),
can mange some operation such as execution of tests from execution with
out opening the Tosca Commander. This approach is used to automate
the triggering of test execution process.
2. Users may use the comprehensive selection of purposes of the GUI
version from the Tosca commander.
3.
Q60) Explain the steps that create test cases through ARA?
Ans: The process steps are –
• Record any scenario using ARA Wizard.
• Add verification points during recording and perform clean up on the
recorded scenario.
• Export the recording.
• Import recording in Tosca.
• Execute test cases which are auto-created during recording.
•
Q61) Specify the different approaches for object identification in Tosca?
Ans: The different approaches to steer the controls during the scanning, for
any test objects are mentioned below-
1. Identify by properties
2. Identify by Anchor
3. Identify by index
4. Identify by image
5.
Q62) What is DokuSnapper in Tosca?
Ans: The DokuSnapper function enables to an archive of the progress of
automated tests in a document. Tosca creates a Microsoft Word document for
every test script upon each execution. The document name consists of the test
script name and the timestamp of the execution time.
User can enable Dokusnapper from Settings
Configure options and settings > Settings Dialog > Settings – Engine >
Settings – DokuSnapper
Q63) What is TDS?
Ans: TDS stands for Test Data Service, which is used for test data management
in Tosca. Using TDS, we can store the dynamic test data in a shared location
which is easy to read/ update by the test case. As the data stored in a shared
location, it is useful to share the same dynamic data across multiple test cases.
Also, we can update it without opening Tosca as it’s treated as a separate
component.

Q64) Explain the API Testing using TOSCA? Explain the advantages.
Ans: API stands for Application Interface. In a multi-application environment
where one application is interacting other application through API, we have to
wait for the completion of development of all the application for testing. So the
testing is going to be a time-consuming process. Instead of that, we can start
the testing of APIs once any of the application is ready to reduce the execution
cycle time. So API testing is an approach to test the interface through API
before integration of the entire application. Tosca provides an API scanning
wizard; through this, we can scan the API and creates API modules. Later
based on the module, we can create test cases to perform Tosca API Testing.
The advantages are –
• Fast execution.
• Reduce execution cycle time.
• Testing can be initiated before system integration.
•
Q65) Explain the exploratory testing features available in Tosca?
Ans: It’s an approach to record test scenarios as a document for functional
analysis, verification/ testing of training purpose.

Q66) How can we change the value of any Test Configuration Parameter
during the execution?
Ans: First, one buffer has to be assigned for the Test Configuration Parameter
(TCP). After that, by changing the buffer value using “Tbox Set Buffer”, we
will be able to change the TCP value during execution.

Q67) Is it possible to automate mobile apps in Tosca?

Ans: Yes, Tosca supports mobile automation using engine ME3.0 for mobile
testing.
Q68) Explain the approach of mobile testing?
Ans: We need to follow the below steps to perform mobile automation.
• We need to connect the physical or simulator mobile device with our
system or Appium server. For an iOS device, we need to connect the
device in Appium configured Mac system.
• Select the Scan->Mobile option while scanning mobile devices.
• In the scan window, we need to provide basic details such as Connection
type as Local or Appium Server, Name of the device, Device Id and
device type as Android or iOS.
• We need to select the checkbox for “Run Live View” to replicate mobile
screen in the device.
• To establish the connection with mobile devices, need to click on
“Connect” button.
• Select the desire mobile screen and scan to create nodule.
• Create the mobile test cases based on the created modules and some
standard modules such as an open mobile app.
• Execute the test case.
•
Q69) What kinds of mobile apps are supported by Tosca?
Ans: Only Android or iOS mobile devices are supported by Tosca. Also, it can
automate mobile web, native and hybrid apps.

Q70) What are the different engine available for mobile automation?
Ans: There is two engines are available –
1. Tosca Mobile + – It’s used for old devices.
2. Mobile Engine 3.0 (ME 3.0) – It’s used for the latest devices.
3.
Q71) What is the basic configuration required to execute any test case in
mobile Chrome browser?
Ans: We need to set the value as “CromeAndroid” for TCP Browser.

Q72) What is ARA?

Ans: ARA stands for Automation Recording Assistant. This is an advanced
recording feature of TOSCA. With the help of ARA, we can record any
scenario with the verification and generate the test cases instantly. After
recording ARA generates a .ara file which needs to be imported in TOSCA to
generate the instant test case. This is very useful for the business user who does
not have any bits of knowledge about Tosca.

Q73) Explain the advantages of ARA?

Ans: The major advantages are –
• Standalone recording wizard
• Intuitive recording
• On-the-fly remarks & verifications
• No duplicate modules in a single recording
• Easy clean-up
• Fast playback
• Easy to export & import recordings
Q74) Explain the limitations of ARA?
Ans: The limitations of ARA are –
• Compatible with Tosca 13.1 & above
• Linear recording
• License required for standalone installation
• Duplicate modules get created in multiple recordings
• Challenging to modify existing tests
• Yet to be compatible with Android/iOS
Q75. What is Vision AI in Tosca?
Ans: It is going to be an advanced test automation approach to automate the
test cases irrespective of the technology of the test application. This approach
will be made with the help of the artificial intelligence (AI) concept while
recognizing the objects through TOSCA AI Scan. Based on looks and
appearances, the objects are getting identified using AI features.

Q76. From which version the Vision AI is available?

Ans: The Tricentis Tosca has introduced these features from Version 14.x.

Q77. What are the features of Vision AI in Tosca?

Ans: The major features of Vision AI are specified below –
• AI-driven Object recognization – Tosa AI engine is capable of
identifying the test objects based on the appearance and looks, without
considering the technology of the application.
• Automate Citrix-based application – We can automate the
applications which are hosted in Citrix.
• Automate under development application – The AI engine is capable
of automating the application before completion of the development.
Here, Tosca is able to automate based on the mockup environment or
based on the designed layout diagram.
• Automation testing can be started from the very early phases.
• Larger varieties of applications can be automated.
• Some modules can be re-used over different applications (having the
same look and feel) irrespective of technology.
• Reduces the maintenance efforts in vision AI.
•
Q78. How Tosca identifies objects using AI Engine?
Ans: The Tosca AI engine considers below aspects to steer test objects –
• The appearance and the position of the test objects.
• Look and feel includes color, size, etc.
• The attached labels of the test objects.
•
Q79. What will happen for the existing tests which are developed through
AI Engine after changing the technology, keeping the same UI?
Ans: There will be no impact on the existing test cases which are developed
with an AI engine. The reason is that the AI engine does not consider the
technology of the application.
Q80. Specify the different object identification methods used by Tosca AI
Engine?
Ans: The Tosca AI engine follows below identification methods –
• Identify by Properties – The properties available based on the
appearances.
• Identify by Index – Based on the repetitions of the same kind of objects.