Tosca Interview Questions
Tosca Interview Questions
Requirements
Test case design
Test cases
Modules
Execution
Issues
Identify by properties:
If at all tosca is unable to identify any control uniquely with the properties that are captured during the
scanning, then we can use Identify by properties and select the required properties to identify the
control uniquely so that Tosca can identify the control and continues the execution.
Identify by Index:
If at all tosca is unable to identify any control uniquely when we have 1 or more controls with same
labelling, then we can use Identify by Index and select the Index of that Particular control to Identify the
Control uniquely.
Identify by anchor:
If at all tosca is unable to identify any control uniquely then we can use Identify by Anchor and Drag and
drop the Parent control information to Anchor dropbox to identify the Control uniquely.
Identify by image:
If at all tosca is unable to identify any control uniquely then by using Identify by Image we can select
particular region in the application to identify the Control uniquely.
3. What is Module? What are the different types are Modules available in Tosca?
Module stores controls Information in the form of list of properties and each test step must be
associated with one module and basically there are 2 types of modules available in Tosca,
Standard Modules.
User defined Modules.
Standard Modules: Standard Modules are the default modules which comes by default and we can use
directly them wherever needed in our test cases, Ex: OpenUrl, Tbox Wait, Close Browser, etc.
User defined Modules: User defined Modules are the application specific modules which will be created
by Automation test engineers according to their requirements.
Verify Action Mode is used to Verify whether the Control is Exists/Enable/Visible or not and Verify
Action Mode is also used to verify the Inner text of any Control.
Buffer is used to store some value, for Ex: We can store innertext of any control to buffer and we can
call that buffer whenever we need to verify innertext of any control.
Static Buffer
o Syntax: {B[Buffername]}
Dynamic Buffer
o Syntax: {XB[Buffername]}
6. What is TCP?
Test configuration Parameter is used to configure/passing some value to the parameters and we can call
those parameters wherever required.
Syntax: {CP[TCPName]}
Synchronization is process of making the Tosca to wait till it identify the Control, we can set some
Timeout duration under Project>Settings>TBox>Synchronization, So Tosca will wait till that time
duration to identify the Control.
Synchronization timeout will make the Tosca to wait till it Identify the Control within the specified time,
suppose if the control is identified in few seconds only then it will not wait for remaining time and Tosca
will movie to next step.
But in Case of Tbox wait, it will make the tool to wait entire specified time forcefully even the control is
identified in between.
Reusable Test Step blocks are Reusable scripts which can be created only under libraries
Usually in any web application we will have some set of actions which needs to be executed in each and
every test scenario, so in this case instead of creating the same test steps again and again in each Test
scenario we will create the Reusable Test step blocks and We can call those references wherever it is
required.
10. What is Business Parameter?
Creating Business Parameters is the only way to pass different values to the Reusable test step blocks.
Business Parameter are reusable parameters which can be created only under the reusable test step
blocks, under reusable test step blocks we can create Business parameters and can link the test step
values with the Business parameters and we can call these Business parameters wherever required and
we can pass the values directly into testcases.
Tosca provides a Standard module called Tbox Take screenshot, we can add this TBox Take Screenshot
within the test cases wherever it is required, one need to give environment as Desktop, Directory
location and file name, so that Tosca will save the screenshot on that particular location.
{Calc[Len(“”””StringName””””)]}
{Calc[Len(“”””{XB[Buffername]}””””)]}
During the execution if Tosca faces any problematic situations to continue the execution due to
unexpected dialog box or popup windows, by considering these problematic situations we can create
the possible required Recovery scenarios to that Test case, so during the execution if Tosca get any need
of those Recovery scenarios, Tosca will be using them and continue with the execution.
Even if Recovery scenario is also fails to continue the execution and finally Tosca will go Cleanup
Scenario and it will the execute steps mentioned in the cleanup scenario and it come out from the
application.
Scratch book is used to perform trial runs while creating the test cases and Scratch book allows us to
execute the scripts in testcases folder level, test cases level and test step level.
And Scratch book displays the flash status of the execution, and the execution status will not be stored
anywhere if we close the scratch book status window, we cannot see those result again.
Rescan is used to update the existing user defined modules with the new attributes and Rescan is also
used to update the existing attributes under the existing modules.
Directly Tosca cannot scan the attributes present under Mouseover in the applications in such cases we
will go the Advanced view and expand the Filter items bar and manual select the required item and we
will add them to the Modules.
WaitOn is used to make the Tosca to wait till it identify the specified control until the specified time
mentioned in Tbox synchronization settings.
WaitOn is a dynamic wait statement, it will just wait till it identify the control and the will not wait for
the complete specified time.
20. What is the use of Tbox Start timer and Tbox Stop Timer?
Tbox Start timer and Tbox Stop Timer is used to measure the execution time of any test cases, we need
to mention Tbox Start timer in the starting of the testcase and Tbox Stop timer and the end of test case.
And we can also insert a verification point to verify the maximum time.
Firstly, we will create the required attributes and instances in excel and then we will convert the test
case to template, we will specify the schema path with excel location and will update the test step
values with the excel attributes and then we will create the Template Instance and Start the
Instantiation.
22. What is difference between Exists and Visible in Verify Action Mode?
Exists is used to check whether the control is exists (or) not, But Visible is used to check though the
control is exists but still the control is Visible or not.
Both Test Configuration Parameters and Business Parameters are reusable parameters but if we need to
pass different sets of values into Reusable test step blocks then it is suggested to use Business
parameters as once business parameters are created, we can call those reusable test step blocks
wherever required and pass the different values directly to the test cases.
Whereas if we use TCP, altogether we must create multiple parameters for multiple set of data, as TCP is
a static value.
24. What is the difference in Executing the test case from Scratch book and Execution list?
If we execute the test case from Scratch book, we will just see the flash status and once the scratch book
is closed, we cannot check the status again and we cannot download the execution report in scratch
book.
If we execute from Execution list, we can keep track of execution status and we can also download the
reports and we can also verify the screenshots in the reports.
25. What all the applications Tosca can automate other than Web applications?
Other than Web applications Tosca can also automate SAP applications, API applications, Desktop
applications, Salesforce application etc.
Verification-Failure: If any verification point is fails, it means if Expected value and Actual value does not
match then Verification will be failed.
Dialog-Failure: During the execution if at all we notice any unexpected popups and if that stops the
execution then we will call it as Dialog failure.
28. Explain how you can use multiple browsers within the same test case?
IF we need to Run the same test case in multiple browsers then we need to go to TCP and change the
Browser to our desired browser and we can run it.
We have a Standard module called Tbox Window Operation, we can use this module and can Maximize
or Minimize the browser.
No, Recovery Scenarios can be executed only from Execution section, we cannot run Recovery Scenarios
from Testcases section.
Performing testing on the same functionality again and again with different sets of data is known as
Data Driven Testing.
To avoid the overwrite of other tester’s results we will create the test mandates in execution section
and execute the tests under the test mandates.
Generally, Tosca won’t allow us to update test case attribute name in any test cases, In order to do that
we need to add one configuration parameter in associated module attribute i.e., ExplicitName = True,
then Tosca allows you to update testcase attribute name.
Exploratory testing means learning and testing the application simultaneously without any
requirements.
Exploratory testing is about learning the product, designing, and executing tests, and interpreting the
test results, all at the same time.
Date and Time expressions, Math and Calc Expressions, Random Expressions, etc.
CI/CD Integration means Jenkins Integration, tell in the interviews that we didn’t integrate Tosca with
Jenkins.
We are doing only web application testing in Tosca, so didn’t get a chance to work on API testing.
We have not Integrated Tosca with ALM (or) Jira yet, we are manually opening the ALM for raising the
defects.
https://documentation.tricentis.com/tosca/1320/en/content/distributed_execution/creating_events.ht
m
https://documentation.tricentis.com/tosca/1420/en/content/distributed_execution/create_and_execut
e_testevents.htm
Constraint Action Mode is used to Limit the Search, it can limit the search until it renders a single
element.
Repetitions are used to execute the test steps repeatedly, Repetitions can apply only for test step
folders, one can give the repetition property value in the test step folder, tosca repeats the execution as
per the repetition property value mentioned in test step folder.
We can use the standard module “Execute JavaScript” to perform browser back,
If we need any attribute more than one time in the test step, then we can specify the
Cardinality property value as “0-N” in the Module attribute.
In the Module we need to add a Configuration parameter with the property name as
“ConstraintIndex” and with the value as tab number as below.
Ex: ConstraintIndex = 1 (For tab 1)
Tosca doesn’t support to run the scripts in different browser resolutions. (For example
if you do Zoom In and Zoom out.)
Tricentis support team response time is more if there is any dependency occurs.
47. What is the Tosca version that you are using?
Tosca Commander.
Tosca Executor.
Tosca XScan (Tosca Wizard)
Test Repository.
Check-in / Check-out mechanism ensures that users don't interfere with each other’s work, If
one user checkout some testcase, other users can’t access that testcase until that checked out
user check-in backs the testcase.
Yes, we can compare 2 pdf files in Tosca by using the standard module called “1:1 Compare”.
In order to compare 2 pdf’s files, Just we need to mention Reference PDF, Target PDF and
Passwords if applicable, and Accuracy percentage and Excluded Pages.
During Instantiation Tosca captures the values from the Test sheet (or) Excel sheet and creates
the template instances for each combinational data.
Whereas Re-Instantiation is used to capture the updated values from Test sheet (or) Excel
sheet.
Straightthrough is basically one of the characters for an instance, we must give the character as
Straightthrough only if the format and data both are valid.