[go: up one dir, main page]
Scribd
Upload
279 views2 pages

INterview Tosca

Control groups allow selecting values from a dropdown list when multiple controls need to be tested together. Elements can be identified by properties like parent, anchor, index, or image. Cardinality specifies how often an attribute can be used. FireEvent notifies the system of a change. Business parameters allow reusable test blocks to have dynamic values. Loops include while, do, and if statements to repeat or conditionally execute steps. Recovery scenarios provide steps to recover from errors.

Uploaded by

Poorna chandra
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
279 views2 pages

INterview Tosca

Control groups allow selecting values from a dropdown list when multiple controls need to be tested together. Elements can be identified by properties like parent, anchor, index, or image. Cardinality specifies how often an attribute can be used. FireEvent notifies the system of a change. Business parameters allow reusable test blocks to have dynamic values. Loops include while, do, and if statements to repeat or conditionally execute steps. Recovery scenarios provide steps to recover from errors.

Uploaded by

Poorna chandra
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Control group :

A group of link, button and radio button controls within a module, When using a Test
step containing control groups, controls are selected as values from the dropdown list

Create Control group:


* Select necessary Module Attributes
* Right Click
* Choose Convert to ControlGroup
* Rename the ControlGroup
Identify Elements in Tosca :
1. Identify by Parent ::
2. Identify by Anchor
3. Identify by Image :: Highly dependent on Resolution,Zoom and Visual changes
4. Identify by Index
Cardinality :
Cardinality. Specifies how often an XModuleAttribute may be used as an XTestStepValue
in one and the same XTestStep

FireEvent :
FireEvent notifies the SUT that the change has been made to the properties of an object
For example, let‘s say a text box allows you to type in a number, but then there is no option to
click enter or submit to alert the system that a number has manually been entered. Instead, we want
to trigger a FireEvent which alerts the system that a number has been entered.
This steering parameter will be added to the ModuleAttribute on which the FireEvent should
be executed. Now the property will be set to the input value specified in the TestCase.
How to use Fire Event :
● Add the steering parameter “FireEvent” to the Module Attribute
● Add the desired Fire Event as a Value

Business Parameters :
Allow the use of Reusable TestStepBlocks even when the test step contains values
that need to be changed in different TestCases.
Syntax : {PL[Business Parameter Name]}
How to use a Business Parameter :
● Create a Business Parameter on the Reusable TestStepBlock itself.
● Name each Parameter
● Create a reference to the Reusable TestStepBlock within a TestCase
● Enter values for each parameter in each usage of the TestStepBlock
Example – Let us say library is created for test step blocks which includes user name and password.
But if for few test cases you wanted to enter different user name and passwords, then business
parameter will help you.

{DATE[][][yyyy]} ---- Current year as a 4 digit number


{DATE[][+2M}[MM]} --- Show months with 2 digits
{DATE[03.25.2016][+3y][dd.MM.yy]} --- Adds 3 years to the base date and
display in the format dd.MM.yy
IQ : Dynamic Expression to get date after 15 working days
{DATE[][+15w][]}
IQ : Dynamic Expression to get date after 2 working days
{DATE[][+2d][]}
IQ : Difference between m and M in dynamic expressions
m - minutes and M - Month
1. Input
2. Select -- Selects a control without any additional actions
3. Buffer -- Saves variable values from the SUT to a local buffer (variable storage
memory) [Project>Settings>Engine > Buffer (display the values we have stored)]
Syntax : {B[Buffername]}
4. Constraint
5. Insert --- Only for Non UI automation
6. Verify --- Checks values of properties in the SUT
7. WaitOn :: Delays the execution of the next TestStepValue by waiting for a specific
property or value; the wait duration is dynamic.
Max duration of Waiton can be changed under :
Settings >> TBox >> Synchronization >> Synchronization Timeout during WaitOn
Libraries [ TestStep Libraries] :
Contains Reusable TestStepBlocks; any changes in the library will automatically update
References in the Test cases
ExplicitName :
It is a Configuration parameter which can be added to a Module which allows a change
in the TestStepValue name which reflects a technical identification.
How to use ExplicitName :
* Add Configuration parameter “ExplicitName” to the ModuleAttribute | * Rename corresponding TestStepValue if applicable * Set the
value to True
Index :
Index numbers objects that have the same properties, or do not have a unique identifier,
in the order they appear on the page, using #1, #2, #3 and so on. ExplicitName allows
Tosca to steer these objects using the index, taking into account any dynamic changes

ResultCount
ResultCount is a property that is the result of a counting process which can be used for
all controls. RowCount and ColumnCount can also be used for tables.

Requirements :
* The Requirements section of Tosca provides a dashboard for simple and effective test
management. It is used for planning test processes, monitoring progress, and risk coverage
optimization.
* Represents functional and nonfunctional demands or expectations of the SUT.
Requirement Set :
Calculate Weight of the Requirement
Weight = 2𝐹𝑟𝑒𝑞𝑢𝑒𝑛𝑐𝑦 𝐶𝑙𝑎𝑠𝑠* 2𝐷𝑎𝑚𝑎𝑔𝑒 𝐶𝑙𝑎𝑠𝑠
■ Damage class: the estimated damage value of an event. The value must be on a
scale from 0 to 10.
■ Frequency class: the estimated frequency of an event. The value must be on a scale
from 0 to 10.
Pareto Principle : 80% of our risk come from 20% of our application

Loops and Conditions :


Loop : Used for running test steps repeatedly; Three types are WHILE, DO & IF statements
Condition : must be met so that the next step may be taken
WHILE statement : Action to execute a TestStep repeatedly until a condition is no longer met (retry
limit is reached); Condition must be met to run
DO Statement : Similar to WHILE statement, but the TestStep is run once before checking the
condition is met
IF Statement : Action to execute a TestStep once if a particular condition is met
Control Flow Diagram : Visual representation of a TestCase; a tab in the working pane
Recovery Scenario
Recovery Scenario Collection :
Folder containing recovery scenarios; can be located on each level in the hierarchy.
Recovery Scenario :
One or more TestSteps used only if an error occurs that would interfere with the regular
test execution
CleanUp Scenario : One or more TestSteps used only if no appropriate Recovery Scenario
is successful
* To use Recovery Scenarios we have to make sure that we have recovery enabled in our Settings.
In Settings, go to Settings->TBox->Recovery. The first 3 define if dialog failure, exception failures
and verification failures should be recovered. Usually you would want only to recover dialog and
exception failure, since verification failures may point to actual errors in your System Under Test.
Constraint :
ActionMode Constraint is used to perform an action on an object or value in a table, but you
need to limit the search for the object by using more than one identifier.
How to use ActionMode Constraint :
● Steer a TestStepValue which by now exists multiple times
● Set ActionMode to Constraint; Select Value to search for all subsequent TestStepValues
necessary to make the selection unique
Automation Specialist - 02
Logical Statements:
Logical statements can be used to combine multiple Conditions.
AND : All Conditions must be fulfilled
OR : Only one of the Conditions must be fulfilled
== : Is equal to
!= :: Is not equal to

Combinatorial methods
 All combinations.
 Orthogonal.
 Pairwise.
 Linear expansion

You might also like