1.

give me an example where i have implemented recovery scenario and clean up scenario
and what are the retry levels available in tosca?

Certainly! Let's consider an example scenario where you're testing an e-commerce website
using Tosca, and you encounter a situation where the "Add to Cart"

button occasionally fails to respond due to network fluctuations or server issues. To handle
this, you implement a recovery scenario and a cleanup scenario.

Recovery Scenario:

In this case, you decide to implement a recovery scenario to handle intermittent failures
when clicking the "Add to Cart" button.

You configure Tosca to retry the action multiple times before considering it a failure. If the
action still fails after the retries,

Tosca executes a recovery step, such as refreshing the page or navigating back to the
previous page, to reset the application state before

retrying the action.

Recovery Scenario:

- Action: Click "Add to Cart" button

- Retry Level: 3 times

- Recovery Step: Refresh the page

In this recovery scenario, Tosca attempts to click the "Add to Cart" button up to three times.
If the action succeeds within those attempts,

the test continues as usual. However, if the action fails three times consecutively, Tosca
refreshes the page to reset the application state and retries the action.

Cleanup Scenario:

Additionally, you implement a cleanup scenario to ensure that any items added to the cart
during the test are removed after the test execution,

regardless of its outcome. This prevents the accumulation of test data in the application and
ensures that subsequent tests start with a clean slate.

Cleanup Scenario:

- Action: Remove all items from the shopping cart

In this cleanup scenario, Tosca performs an action to remove all items from the shopping
cart at the end of the test execution, regardless of whether the
test passes or fails.

2 .Retry Levels in Tosca:

Tosca provides different retry levels to handle test execution failures gracefully. These retry
levels determine how many times

Tosca retries an action before considering it a failure. The available retry levels in Tosca
include:

Retry with Same Value: Tosca retries the action with the same input value.

Retry with New Value: Tosca retries the action with a new input value (if applicable).

Retry with Initial Value: Tosca retries the action with the initial input value.

Abort: Tosca aborts the test execution after a specified number of retries.

In the example above, we used a retry level of "Retry with Same Value" with a maximum of
three attempts before resorting to a recovery step.

During the interview, you can explain how you implemented these recovery and cleanup
scenarios in Tosca, emphasizing the use of retry levels

to handle intermittent failures and ensure the reliability and stability of the test automation.

3 .Risk-Based Testing in Tosca Test Suite:

Risk-based testing is about focusing your testing efforts on areas of the software that are the
riskiest or most critical to the project.

How Tosca Supports it: Tosca Test Suite allows you to prioritize your tests based on the risks
associated with different parts of your software.

You can identify high-risk areas and ensure they get more thorough testing coverage, while
lower-risk areas may receive less attention.

Tosca provides features for risk assessment, allowing testers to analyze and prioritize test
cases accordingly.

Model-Based Testing in Tosca Test Suite:

What it is: Model-based testing involves creating models of the software's requirements and
then automatically generating test cases

from these models.

How Tosca Supports it: In Tosca Test Suite, you can create models that represent your
application's functionalities, workflows, or user interactions.
These models serve as a basis for generating test cases automatically, saving time and
effort in test case creation.

[Link] Merging:

[Link] can merge the modules by selecting the particular module and go to top and click on
find duplicate modules and then we wil list of duplicates

and select one which one we need and click on merge and thats all it worked.

[Link] can also select 2 modules and click on merge on top menu of modules and we can
merge single element or mulitiple elements into other module.

[Link] to identify elements which have dynamic properties in tosca?

[Link] Dynamic Properties:

Dynamic properties are attributes of elements in the application under test (AUT) that
change frequently.

Examples include IDs, names, or XPath attributes that are dynamically generated by the
application.

Identifying Stable Attributes:

Look for attributes that are less likely to change, such as labels, surrounding text, or other
unique identifiers.

These attributes can serve as anchors to locate elements with dynamic properties.

Using Parent-Child Relationships:

Utilize parent-child relationships to locate dynamic elements within a more stable context.

For example, if a dynamic element is always inside a specific container, you can first identify
the container using stable attributes, then locate the dynamic element relative to it.

​ ​ ​ ​

[Link] Methodology:

Its a process of iterative and incremental approach in order to build piece of software.

Here Iterative means keep on repeating particular process

here incremental means implementing some features of software and keep on adding
additional features of the software.

ex:
login functionality ------------In the login functionality implementing some features like url and
keep on adding the additional features

to the exisisting software with register and next login details .

[Link] is a table and we have N no of rows and at every row we have button and should be
clicked .how to do this?

steps:

[Link] we need to know row count of a table.

[Link] create a folder and drag the test step of the table in this folder and then repetetion
folder will be created.

[Link] here in the folder properties repetition add some repetetions with {MATH[{B[1]}+1]}

[Link] In the table consists of rows and Columns so here in rows mention ${repetetion} and
in the cell select button{REPETETION} and provide some action mode which is buffer.

1<=30

[Link] me an example for math function?

steps:

[Link] create a buffer name as number with value 0.

[Link] a folder for test case and copy the test step in this folder and in this mention
repetations for 5 times .

[Link] repetetion folder is created and in this test step provide in the value as
{MATH[{B[number]}+1]}

[Link] the test case and output as 5 repetations from 1 to 5 values as output.

[Link] Character in tcd:

In the test sheet we have instances for the particular attributes and in that instances when
we check the properties regarding instances we have character and position and in the
character we have valid and invalid and straight through here which is toggle character and
when we put the staright through character it will be in toggle character which is at higher
risk and by default we will have position as inner and valid means we dont expect any errors
and invalid means we expect errors in the test case while executing.

[Link] Mandates in tosca:

In a multi-user workspace, several testers should be able to execute the same tests
simultaneously. They should also be able to execute these tests

​ ​ ​ ​ ​ ​
independently, so as to not overwrite other testers' results. In order to implement this test
mandates go to the execution list and click right click and select test mandates symbol and
then we can create and after that drag the particular test case which needs to executed in
the mandate folder and execute the required test case. So when multiple testers are
executing the test case it will not overwrite the results.

​ ​ ​ ​ ​ ​

11. Synchronization:

Synchronization mechanisms synchronize data between a local workspace and a common

repository. Synchronization is only available in multi-user environments.

​ ​ ​ ​

For the synchronization we can set the values for test case folder :

[Link] default is on

[Link] default is off

[Link] not be excluded

[Link] not be excluded for whole tree.

[Link] do we import data in excel to tosca?

[Link] single test case scenario in order to implement different data in the tosca from excel we
can uilise test template instance means instantiation which has

all different types of data in it so to get test template instantiation we need to convert the test
case template to instantiation and provide the excel path and worksheet here.

2. In different test cases in order to import the data to tosca we can use standard modules
which is excel engine and we can utilise in different test cases

and provide in the test steps with open excel and range and path all the details which are
standard modules .

[Link] you done dex setup?

1. It is used to do parallel executions which can be executed from TOSCA Commander,

qTest , Any DevOps Tools like AzureDevops , Jenkins.

2. User should create Test Events in TOSCA Commander and Link the Execution list which
needs to be executed in DeX.

14 .Synchronization types:

[Link] timeout:
Here basic standard time for the each test case which is 10 seconds and if we want more
time to perform a task then we are

going to set the time duration more by creating configuration parameter and provide
synchronization timeout 20000 ex...

​ ​ ​ ​ ​ ​ ​

​ ​ ​ ​ ​ ​ ​

[Link]:

In order to implement this fist for waiton the standard time will be 20 seconds and if you want
more time then create

synchronizationTimeoutDuringWaiton for particular test case and add more time like 30000
which is 30 seconds.

​ ​ ​ ​ ​ ​ ​

​ ​ ​ ​ ​ ​ ​

[Link] i have 100 modules and i dont know where i need to rescan , so whats your
approach?

Steps:

[Link] we are having 100s of modules so we dont know where to scan now we have decided
to rescan so from the particular test step we will go to exact module

which we want to rescan and implement the task regarding rescan.

[Link] will be done whenever the particular elements are not mapped or more than one
control found , in order to rectify those mistakes the approach is

rescan.

[Link] is a case where my test cases are passing in the scratchbook and not able pass
my test cases in execution list?

Steps:

[Link] sometimes there may be an issue in the properties of that particular element which
we have scanned in order to implement in that test case.

[Link] sometimes in order to move from one page to other page we may forget to give wait
on in order to wait for sometime and perform the task .

[Link] may be sometimes configuration parameters may wary for browsers like internet
explorer and google .
This are all the reasons may work at scratchbook and not in execution list.

After running the cleanup scenario, Tosca will proceed to the next test case in the test suite,
assuming the cleanup scenario executed successfully.

If the cleanup scenario fails, Tosca may halt further execution depending on the test suite
configuration.

[Link] are the excel modules we have in tosca?

We have standard module which is excel in the tbox x engine so we can implement from this
excel standard module there are some methods :

[Link] excel workshop

[Link] range for excel

3. excel range manipulation

[Link] excel

[Link] are the parameters we will select in order to make elements unique in properties?

properties are classname,id ,name,innertext, visible innertext,outertext , tag etc..

19. The TBox Evaluation Tool:

The TBox Evaluation Tool is a Tosca expression evaluation tool that allows users to compare
values and provide a true or false result.

The tool can handle any type of dynamic expression, such as comparing a buffer with
another buffer.

[Link] do you manage the data?

In order to manage the data all the records will be stored in a repository which we caan
delete or modify the test cases as per required.

so in order to manage the data the test data services are installed by default in the tosca
commander and through that we can manage the data.

Have you Customize reports:

[Link] Between Selenium and Tosca?

Selenium is an open sourse automation tool and it allows to test web browsing applications
and it requires coding knowledge and in order to test the web applications.

Tosca is licensed based automation tool and allows to perform testing on software
applications and here just we should know correct approach to work with tosca.
[Link] Estimation in Azile?

Estimation which needs to complete the task in particular period of time in order to test the
software in the project related to starting time of the task and

ending time of the task of the project.

[Link] of my sprint?

Here sprint capacity means the team must complete the task in order to test the application
or software in particular period of time.

so we follow these things which are planning and continous improvement .

In the planning the task will asign to each and every individual and based on test skills and
test the software and complete task on the sprint. And there will be continous improving in
order to test piece of software in that sprint.

[Link] are not reproduce at developers side but it is reproducing at QA side . Resolution?

There may be several reasons for that:

[Link] may be a communication gap between testers and developers.

[Link] may be a problem with environments versions variations and configurations issues.

[Link] to review test cases once again whether all the test steps are executed for a piece of a
software.

[Link] check regression testing is done if it is necessary .

Both Tosca and Selenium are suitable for application testing, but Tosca is more aligned with
the concept of a comprehensive Test Automation and

Continuous Testing Platform, making it suitable for both application testing and migration
framework needs.

[Link] end of a Product Backlog Item (PBI)

The end of a Product Backlog Item (PBI) is typically marked when all its requirements and
acceptance criteria are met, ensuring its successful completion

within the sprint timeline.

[Link] for regix and /d means

{REGEX["Regular expression"{B[Buffername]}"Regular expression"]}

{Regex["[a-z]* (?<username>[a-z|\d]*)!"]}
here /d means expression which identifies length of the string and consists of characters and
numbers.

a-z means expression which consists of length of string with whitespace.

[Link] life Cycle:

[Link] defect which is identified by tester by utlising the defect tracking system with the
details of severity, priority defects.

[Link] developers will check the defect and start working on defect and address the issue in
the code.

[Link] developers will fix the defect and inform to testing team and again the testers will do
re testing becuase for that particular bug or defect

it should not effect the exisisting softwares thats the reason it will check total build or
software .

[Link] last if the bug is rectified then the defect will be considered as resolved as per
requirements.

[Link] types of errors found in execution list ?

[Link] on failed

[Link] has failed

[Link] than one control found.

[Link] credentials

[Link] timeout

[Link] errors

[Link] test cases for payment page in e commerce application?

Validating the payment page :

[Link]:

[Link] address

[Link] mode

[Link] information

[Link] confirmation

[Link] id
[Link] Cascading:

When one defect leads to discovery of other defects the major reason behind this the
particular defect is not fixed properly.

ex: Math functionality defect is not fixed properly so we can get lot of issues like
miscalculations of that defect.

​ ​ ​ ​

[Link] to achieve dynamic wait in tosca?

In order to implement dynamic wait just provide wait on and by default wait on is 20seconds
and if we want more time we can provide synchronizationTimeoutDuringWaiton and provide
duration time as per required.

[Link] parameters and business paramters:

In the test case folder or test step we can create test configuration paramters in order to
work with the test case or test step and there are some test configuration parameters like
ToscaDateFormat, ToscaTimeFormat,TocsaDateTimeFormat and Browser and
Synchronization and SynchronizationTimeoutDuringWaiton etc..

mostly these are all the parameters we will utilise in the test case or test step.

​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​

Buisness parameters: In order to implement the business parameters first we should have
RTB and for the RTB folder we should have business parameters

in order to implement the parameters because the RTB can be implemented and can be
used in other test cases as per required and

when ever the business parameters are parameterised then in the RTB w can observe
syntax for Parameter like {PL[url]} ex...

[Link] to justify bug raised from tester point of you?

We can identify the bug by testing functionality of application and if the functionality is not
working according to user expectations and specifications then we can

easily tell the bug is identified and then we will inform developers team and this team will fix
the bug at code side and they will inform to testers team and

testers team will retest that functionality which is failed and this process goes on.

In Tosca, "Fire event" typically refers to triggering a specific action or event on an element,
such as clicking a button or entering text into a field.

[Link] automate interactions with a webpage and its pop-up in Tosca:

Use Tosca's Browser and Web modules for navigating the webpage and interacting with
elements.

Utilize Popup Interaction module to handle the pop-up, configuring actions like clicking
buttons or dismissing alerts within the defined time frame.

[Link] is n and n+1 versions and how you will you test?

we will do different types of testing based on versions like

[Link] testing

[Link] testing

[Link] Feature testing

[Link] testing

[Link] testing

[Link] testing

[Link] Mode for Buffer?

Verify which is action mode for dynamic buffer.

Regular Expression: is used to verify and extract the dynamic parts of a string .

Syntax: {REGEX["Regular expression" {B[BufferName]} "Regular Expression"]}

[Link] in Tosca?

Tbox framework and classic framework

[Link] of Image identifier in tosca?

[Link] allows to interact with user interface elements based on visual appperance.

[Link] most of time we dont implement in real time projects because mostly we will
use properties, anchor, index.

[Link] in past version and present version of tosca?

[Link] is highly secured compared to previous version.

[Link] usability is also more and it is more user friendly to use the app.

[Link] performance is also good and it is little bit slow with the previous versions.

[Link] for close browser without using standard module ?

{SENDKEYS[ALT+F4]} we can use sendkeys by creating buffer close browser name and
mention value which is {SENDKEYS[ALT+F4]} and action mode is input.

Alternate for open url without using standard module that is start program we can also use
this and provide the path and browser and arguments if needed.

[Link] repositories supported working with multi user workspace?

[Link] repository

[Link] data management Systems

[Link] Control Systems.

[Link] between check out and check in all and checkout tree and update all?

Checkout:

user can do the work regarding test cases or test steps and no other tester can access the
work at the same time.

Checkin all :

user can access the work regarding test cases or any task which previous user had done to
view or modify the test steps.

Checkout tree:

user can access the whole structure or sub folders at at time and do the work regarding total
modules or test cases as per requirement.

update all:

When we use update all then the objects or elements will be updated in the server to the
latest version.

​ ​

[Link] of Multi user repository:

[Link] select type of repository

[Link] the Connection string

[Link] create workspace when the multi user repository is created for the first time and later
from second time just provide slim workspace enough.

[Link] after opening multi user repo first we need to click on update all because we need to
update objects in the local workspace to latest version.

5. And click on check out to work or edit or modify the task.

[Link] zenith wants to scan the attributes and other person needs to check in all and he is
not available right now so what will you do in this case?

In this situation zenith will create another folder and checkout from that and implement the
task regarding scanning and other option is we will ask the admin because

admin will have all rights for checkin all option this are 2 options we can implement.

[Link] Strucure in tosca?

In the reporting section we can have details regarding execution list in which the test cases
are executed and Requirement management and test cases

which are passed or failed.

In Tosca, issues with scripts can be handled by debugging and troubleshooting using the
built-in Scripting Engine functionality.

[Link] failures while using verify action mode ?

Verification failure due to element not found or not visible on the screen.

Incorrect text or value displayed on the element being verified.

Timing issues where the verification is attempted before the element is fully loaded or
available.

Unexpected changes in the application's UI structure or layout, leading to verification errors.

Discrepancies between the expected and actual results of the verification condition.

[Link] defination:

Its a file reference and can be used as a reference of excel template.

The template can be used as a data source for a test case template.

[Link] Date format :

It represents the date within the tosca test scripts,modules ,or test data.

ex: [Link] , [Link] , [Link]

[Link] time format:

It represents the time with in test scripts ,modules, test cases.

ex: [Link] --- 3.50pm

[Link] --- 15.50 30

​ ​ ​ ​ ​
​ ​ ​ ​ ​

[Link] using action mode wait on and still not able find the control to steer means maximum
time is exceeded and and i dont want to change settings it will impact on test cases , so tell
me what to do for test case level and for partilcular attribute level in tosca explain details with
clear steps take time and explain me and use basic english and i need to understand

For Test Case Level:

Step 1: Identify the Problem: Determine which specific test case is experiencing the issue
with the "Wait On" action mode exceeding the maximum time limit.

Step 2: Review the Test Case: Analyze the test case to understand why the control is taking
longer to appear than expected. It could be due to network latency,

slow loading times, or other environmental factors.

Step 3: Adjust the Timeout: If changing global settings is not an option, you can adjust the
timeout for the problematic step within the test case itself.

Step 4: Set Local Timeout: In Tosca, you can set a local timeout for individual steps using the
"Wait Timeout" property. This allows you to override the global

timeout setting for specific steps within the test case.

Step 5: Test and Validate: After adjusting the timeout for the problematic step, execute the
test case again to verify if the issue is resolved and if the control is

found within the specified time limit.

For Attribute Level:

Step 1: Identify the Attribute: Determine which attribute within the control is causing the
delay. This could be related to the identification strategy, properties,

or other attributes of the control.

Step 2: Review Attribute Properties: Examine the properties of the attribute to understand if
there are any specific settings or conditions causing the delay.

Step 3: Adjust Identification Settings: If necessary, adjust the identification settings for the
attribute to improve accuracy and efficiency. This may involve

refining the identification strategy, updating properties, or using alternative methods to locate
the control.

Step 4: Test and Validate: After making adjustments to the attribute settings, retest the test
case to ensure that the control is located within the expected time

frame without exceeding the maximum wait time.

By following these steps, you can address timeout issues with the "Wait On" action mode at
both the test case and attribute levels in Tosca without having to change

global settings that may impact other test cases. Adjusting timeouts locally and refining
attribute properties can help improve the reliability and performance of

your test automation scripts.

[Link] helps to get nearest no

n=15.05

n1=[Link](n)

print (n1)

[Link] can transfer or get the data of excel to tosca in 2 ways:

[Link] using standard modules excel engine and provide open and path and range and
manipulation and close the workshop.

[Link] in the test case we can convert to template and edit schema path and provide path
for excel and get the data.

[Link] a table i dont know row count and after every last row i need to click a button then next
set of rows will be visible .So repetetion i wil do continously to rows. How do you do that?

Steps:

[Link] the test case we will create or drag the test step regarding table and in that table we will
know the RowCount first.

[Link] in the particular test case i will create folder which is loop folder and in that i will drag
the module table which i have scanned.

[Link] in the loop folder in the properties i will take as {MATH[{B[buffername]}+{Repetation}

[Link] the folder table we have rows and cells in that i will take it IN ROWS as ${Repetation}
and in cells i will mention last row and in next cell i will create embeded control

for that cell which is button means click on button and then execute test case.

[Link] section in tosca?

It covers the broad spectrum of functionalities related to requirements management,

including scanning requirements for modules, implementing test cases based on
requirements, analyzing reports, and managing project requirements.

[Link] TOSCA, you can dynamically run test data at runtime by:
Utilizing parameterization: TOSCA allows you to parameterize your test data, enabling you
to pass values dynamically at runtime rather than hardcoding

them into your test scripts.

Integrating with data sources: TOSCA offers integration capabilities with various data
sources such as Excel sheets, databases, or RESTful APIs.

You can fetch test data from these sources dynamically during test execution to ensure
flexibility and reusability.

[Link] is TQL and what is sub part and super part in tosca?

In Tricentis Tosca, TQL, or Tosca Query Language, Subparts and Superparts are operators
that search for child and parent elements.

Subparts searches all the child elements in TOSCA, while Superparts searches for parent
elements.

[Link] saturday date :

{DATE[04.04.2024][+3d][]} ---- here first square bracket is actual date and second square is
offset which is calculation and third bracket is expected date

[Link] the use of un attended mode of execution in tosca?

In order to implement this unattended execution in tosca we should have graphic user
interface and and set up un attended execution in tosca and even though screen is locked
and without user logged to machine the test cases will be executed.

[Link] can we find logs for recovery scenario?

[Link] recovery scenario is part of test case module and open tosca commander

[Link] on execution list and here go the test case which is executed and in detailed logs of
the test case we can have related to recovery scenario and through that we can logs related
to triggering will be done in here.

[Link] utilising execution list in tosca we can understand how the logs are managed in the
recovery scenario .

[Link] tosca we have Control groups in order to use for links ,buttons, radio buttons like
provide the link and control name and action mode which is input.

We can select multiple rows in tosca by selecting shift and then select the no of rows we
need .

[Link] event in tosca?

"Generic List" is like a simple list of items you can create. You can use these lists to store
things like usernames, passwords, or URLs that you need for your tests.
They help you reuse the same set of items across different parts of your tests, making it
easier to manage and change them when needed. For example,

you might use a Generic List to store different usernames and passwords for logging into
your application during testing.

In TOSCA, configuration parameters are used within node templates to specify various
operational settings such as IP addresses, ports, credentials, and other

configuration details.

These parameters are defined in the TOSCA service template

[Link] can be both functional and non-functional, depending on the perspective from which
they are evaluated.

Functional Perspective:

From a functional perspective, an API is considered functional if it performs the tasks or

functions it is designed for. This includes functionalities such as retrieving data,

updating records, performing calculations, or executing specific actions based on the

requests it receives. Functional testing of APIs focuses on verifying whether

the API behaves as expected in terms of its functionality.

Non-Functional Perspective:

From a non-functional perspective, an API is evaluated based on its performance, reliability,

scalability, security, and other quality attributes.

[Link] expressions in Tosca?

[Link] Numbers -----------zenithpuli{RND[2]}@[Link]

[Link] Text -----------{RANDOMTEXT[12]}

[Link] --------{DATE}

[Link] --------{TIME}

[Link] types of ways to identify objects in tosca test suite

[Link] by properties

[Link] by anchor

[Link] by image

[Link] by index
To scroll down the web application then we can utilise scroll operations like verticalfirst and
horizontal first as per required.

[Link] to find duplicate modules in standard modules?

[Link] to the particular scanned module and select find duplicate module option on right side
of top .

[Link] on that and we can find any duplicates regarding modules.

In order to merge module first find duplicate module and then we can have merge all option
in find duplicate module.

[Link] Modes in Tosca:

[Link]

[Link]

[Link]

[Link]

[Link]

[Link]

input: It allows to enter some random data

Insert:It is mainly used in Non UI interfaces like XML.

verify:It allows to verify some data whether it is true or false

buffer:It is a variable which stores values

partial buffer

dynamic buffer

set buffer

accesss buffer

delete buffer

Constraint:It limits the search for particular element in test case ​ ​

Wait on: It allows the particular element for period of time to go and perform some action

​ ​

[Link] not possible to launch more than one browser in single test case
in order to run the test case in particular browser we will use test configuration parameter
and mention name and value like browser with google or any browser name .

[Link] inner text property keep on changing then how do you identify element uniquely?

By providing inner text= demo* here demo is text in the technical properties.

[Link] to achieve data driven technique in tosca?

Steps:

[Link] a test case with folder structure as per required.

[Link] convert the test case into test case template so from template we cant run the test
case thats the difference between test case and test template.

[Link] the test case design create a test sheet for tcd folder and provide some attributes and
instances for them and here attributes are like parameters and instances is

like values and when we are trying to create attributes we get additional properties like
character and position and we have values for them like valid and in valid and

straight through and it is toggle character when we implement straight through and poistion
which is inner by default.

[Link] when creating test sheet we can generate instances with combinational and orthogonal
and dynamic expression as per required.

[Link] after creating test sheet we can drag that test sheet into test case template and from
there we can observe here schema name and schema path with the test sheet name

[Link] Convert the test case template into test case instantiation and then we can see all the
excel format data with total structure with positive and negetive scenarios.

[Link] in mind that while data is stored in TCD we should not enter the data in test case ,the
data should pass in TCD with attributes and instances and create test sheets to store

the data.

class reference:

If the particular attribute is keep on repeating again again then we can implement using class
in the test sheet then tosca creates class reference in order

to utlisize attributes and instances in the test sheet.

resolve class reference:

we can remove the class in the test case design by using right click and select resolve class
reference from menu.
The Frequency class in Tosca is used to calculate damage values for specific events based
on quantity in terms of frequency. The values range from 0 to 10 (minimum to maximum).

Relations :

It allows to generate instances like dynamic expansion in test case design based on
buisness requirements.

​ ​

[Link] can find first value with same data in table

with row mention #1 and action mode which is buffer

[Link] operations:

[Link] of the string:

First set the buffer of that buffer name and give some value like string with automationstring

Here to find out length of string so provide

lengthofstring -------{STRINGLENGTH[{B[string]}]}

[Link] to find small to capital letters then go for

upperstring buffername ---- and in the value mention {STRINGTOUPPER[{B[string]}]}

[Link] to find capital to small letters then go for

lowerstring buffername ------and in the value mention {STRINGTOLOWER[{B[string]}]}

[Link] to get replaced with other string then go for string replace

stringreplace-----buffername and in the value mention

{STRINGREPLACE[WeekEnd][e][x][IGNORECASE]} ---here ignore case means ignore small
or capital letters

doesnt matter to replace

{STRINGREPLACE[{B[weekend]}][e][z]}

[Link] search

stringsearch----buffername and the value is mention

[Link] of occurence of a string :

no of occurence ---buffername and in the value mention

{NUMBEROFOCCURRENCES[{B[string]}][T][IGNORECASE]}

HERE ignore case doesnt matter whether it is small or capital letters for t in order to count.
7.{TRIM[ no starting space ][START]} ----here starting means removes spaces at starting

{TRIM[ no starting space ]}

removes white spaces in the string.

[Link] the values from a string and verify ?

create a set buffer and with name Tosca and with value which is Automation Tool and with
string data type.

and provide the buffer name and provide value and with action mode which is buffer .

and now verify the value of automation tool of buffer name which is Tosca is valid or not?

so provide the same buffer name which is Tosca and value which is Automation Tool and
verify which is action mode.

[Link] we have a table and it has duplicate values first name as shiva and i want you
to click second occurance of shiva ?

so here mention in the table of row with #2 and mention the action mode which is buffer.

[Link] to open a file in tosca?

we can use standard module which is t box open file and provide resourse and file path so
we can open the file.

[Link] to find the file downloaded into the system?

we can use file existences standard module provide directory and file name

[Link] to upload or create file?

we can use create file standard module and mention directory and file name and text which
is content.

The default action mode for test step value when creating new test steps

action mode is Donothing

[Link] to compare the values in tosca by using t box evaluation tool.

we can compare two dates or 2 buffers or 2 times by this evaluation tool.

[Link] incognito mode in chrome ?

shortcut is control +shift +N

[Link] count:
To verify how many attachments a message contains and for the files use action mode which
is wait on

​ ​ ​ ​

Column count ---------No of columns in a table

row count -------no of rows in a table

[Link] difference

First set buffer with date difference and value metion syntax is

{CALC[DATEDIF(DATE(2024,04,20),DATE(2024,04,26),"""d""")]}

output is 6

{CALC[DATEDIF{DATE(2024,04,20),DATE(2024,04,26),"""d""")]}

{CALC[DATEDIF(DATE(2024,04,20),DATE(2024,04,26),"""d""")]}

{CACL[DATEDIF(Date(2024,04,20),Date(2024,04,29),"""d""")]}

[Link] way for close browser in tosca ?

t box send keys mention caption name demo*

and mention keys with %"{F4}"

[Link] function :

when we enable this it will generate the word document for every test case upon each
execution.

​ ​ ​ ​ ​

[Link] event :

{MATH[{B[num1]}+{B[num2]}]} and in order to implement this provide steering parameter

FireEvent is input and implement in the test case.

insert action mode is used for non UI like xml

[Link] Codes :

200 success or okay

201 created

202 Accepted

204 No content
400 bad request

[Link] methods

1. Get ---- get some information

2. Post ---- create data as per required

[Link] ----- modify the existing data

4. Delete ---- delete the data

[Link] can get data in xml or json format as per required and mostly we will get in json
format

{ "name": "Puli zenith sai",

"Age" : "30"

[Link] modules in data base in tosca?

[Link] DB Expert

[Link] Connection

[Link] SQL statement

[Link] planning :

In order to implement the test cases or execute the test cases we need to have a plan bases
on builds or steps of a software and in order to

create a test plan the session owner will create session and add members and assign the
task and add duration as per required builds and

needs to complete the task in that sprint as soon as possible and without plan we cannot
implement the test cases.

​ ​ ​

[Link] expressions in Tosca?

[Link] number

[Link] Text

[Link] and TIME

[Link] to get data from first row to last row in second cell customer names we can
use while condition loop
step1:set buffer for the test case with num buffer name and value as 1

step 2:drag the table from module section and implement in the test case so here we got the
table and know the RowCount of that table and provide

value as Row and buffer the Row which is value. So we got the RowCount as 6 with row
value is 6.

step3:Here provide the while condition with loop and here in the condition provide evaluation
tool to know the diff between 2 values and

so here in the evaluation provide {B[Row]}>{B[num]}. we will check the condition with 6>1 so
satisfied.

step4 :go to loop and here drag the table and here in row mention ${B[num]} and select
action mode and in the cell mention

$2 because we need the second cell information so provide in the value with name{B[num]}
and action mode which is buffer.

step 5:set the buffer in the loop with num and provide value with {CALC[B[num]}+1]} in order
increment the values. so here now num is 2

step 6:so here again check the condition with 6>2 and process will be keep on going till 6>6
is not satisfied. so we will get the values till 5 rows

current company client:

tech mahindra

​ ​ ​ ​

​ ​ ​ ​

spring infotech company: pay role

experience:

4.11 months

​ ​ ​

​ ​ ​

​ ​ ​
​ ​ ​

manual:

​ 1.6 years

tosca:

3.5 years

current salary:

5.5 lpa

expected 10 to 11 lpa

If i want to provide path in open excel where the file is stored in your machine and if other
person run that particular test case it will fail because the path

of file changes or path doesnt exists .so how will you handle this type of situations.

Steps:

I will save the excel with in project location not in the local machine so that every one can
access who is in the project level.