13/12/2024:

Tosca Training Course Content:

 Basics to Advanced level topics (Modules/ Testcases/ Requirements/ Execution/ TCD/
Configuration/ Issues)
 Test Data Mangement with TCD/Excel/TDS
 Web, Desktop, API, SAP, Salesforce, DB applications
 Dex
 Vision AI
 Tosca Copilot (14 trail Version) – End of the sessions
 Assignment – each and every area
 Daily Notes
 Recordings
 Random Applications (Multiple Applications)
 Interview Questions (3 to 10 Years)
 Guidance on the Profile preparation
 Duration: 30 to 45 Days (+5 or -5 Hours) = 50Days (50 Hours)

Tosca Features:
Functional Test Automation Tool (Image comparision, Extract text image)
100% Scriptless (If you want there is facility use coding part as well)
TBox Start Program – path (Arguments)
175+ application we can automate, BI,Dashboards
We can integrate with Test Management (ALM, qTest, RQM, JIRA) – We run from TMT
We Test coverage (%?)

Tosca Components:
Testcases/Modules/Execution(Scratch Book)
Drag and Drop method in tosca
Module: Technical information Application

Tosca License: Trail Version (8weeks) – Extended

DI – Data Integrity
AI – Features
TCD/TDS/DEX

14/12/2024:
Registration and Set up for Tosca:
https://support-hub.tricentis.com/ and Register

Tosca Application path:

License Request: https://support-hub.tricentis.com/open?id=training_license_request

Installation Process:
Double Click on the .exe file and Complete the process by clicking on Next, Next and Finish.
Completed the Installation Process in Above steps:
Repository:
1. Single User
2. Multi User
Single User: Activities you are doing it saved local and not allowed others to see your changes or
activities.
Multi User: The all people which comes under same repository can access. Common
repository(MYSQL/DB2/Oracle…)

SQLite – Training purpose and look and feel of Multi User Environment
Real Time: Oracle, Ms SQl Server, DB2
Sqlite : Training or learning

Single User WS: No DB. Tasks in saved in local machine and you can see your tasks in
Commander
Repository Name: None
Multi/Shared User WS: Multiple people can login with Same repository and they share the tasks in
between testcase.
CheckinAll → Save our test case development in Repo
→ Push code into Repo
→ Entire Project COnvert into Read Mode
UpdateAll
→ we are able recent updates in workspace(Project)
→ Entire Project COnvert into Read Mode

Checkout
Particular folder
→ apply each section and select the folder and do the checkout.

CHeckout Tree:
→ Along with Parent and Sub Folders are blocked for Usage .

18/12/2024:
Tosca Commander Tabs Section for Sample Process flow:
Modules
Test case
Scratch Book
Execution

Modules:
Technical information of the Application
 Used for creating TestCases
 Module contains technical information of the SUT
 Modules collect information via XScan XScan Scans various applications, interfaces, visual
and non-visualtest objects
 To steer an object, it must be uniquely identifiable Use technical properties to identify e.g
User ID, Name, InnerText, OuterText.
 Acting as repository for the AUT in Tosca commander.

Folder Structure:

Module Hierarchy:

Module Root folder → Scan → New → Application

Module Subfolder —> Scan → New → Application

Module → Rescan
Module->Scan->Application:

XScan window Options:

1. Basic View

Finish Screen: To Save Module

Condensed: Minimized Xscan window
Advanced: To switch other view
Close: close xscan
2. Advanced View
Properties of the Objects:

Technical Properties:
Tag, InnerText, Class, InnerHTML, OuterText, OuterHTML, Id(Optionally)
Representation Properties:
Default Name, AssociatedLabel, Visible
19/12/2024:
Object Identification Controls:
These are going to used when object is not identified uniquely(After changing properties)
1. Identify by Properties
This is the Default method to identify the objects uniquely if still not identify uniquely
then we will go with Anchor
2. Identify by Parent
Parent and Child to be identified uniquely.
3. Identify by Anchor
We are giving another object associating to identify current object uniquely.
We are landmark to current object.
Not Uniquely Identified: After Anchor (Look for another Anchor Control)

4. Identify by Image
 5. Identify by Index

Rescan :
Already scanned module
Module → Rescan → select control
1. Adding new control to the existing module
Unmapped:
→ existing Module Attributes is not there in rescanned page then those module
attributes goes to the unmapped section
→ existing Module Attributes are there in the rescanned page then those module
attributes are in the unmapped section, that Module attributes are not unique.

Click: Here mouse movements

X: Directly perform the action

****Self Healing(To be Discussed)*****

23/12/2024:
Standard Modules:
OpenURL Module = Launch application (Edge/Chrome/Mozilla)
Default Browser = Edge
Open URL Module:
TCP : Test Configuration Parameters
TCP will work as Global Variables and we will define these TCP’s in TestCase Root Folder,
Test Case Sub Root Folder, Testcase level

TCP is having Predefined Parameters and we create our own Parameters as well
1. Predefined TCP’s
a. Browser
b. Synchronization
c. TargetDateFormat
d. TargetTimeFormat
2. User Defined TCP’s
a. UserID
b. Password
c. URL’s
Syntax : {CP[ParameterName]}
{CP[Browser]}
{CP[Demo_UserID]}
{CP[Demo_Password]}

Create TCP’s in TestCase:

Define TCP’s in TestCase:

Basic Windows Operations:

 1. TBox Take Screenshot
C:\Tosca_Projects\ToscaCommander\Screenshots and
Filename: Date and time
⇒ Project Setup:
Project→ settings → Tbox → logging→ screenshots
⇒ How to take screenshots of failed test steps?
Project→ settings → Tbox → logging→ screenshots
Make screenshots on failed test steps ⇒ verification failure.
⇒ Doku Snapper
Creates a word document, it stores the default location.
→ enable this Doku snapper.
C:\Users\Admin\AppData\Roaming\TRICENTIS\TOSCA TestSuite\7.0.0\dokusnapper

TBox Star Program:

24/12/2024:
TBox Start Program:
Incognito Mode of Chrome:
Path: C:\Program Files\Google\Chrome\Application\chrome.exe
Argument : -Incognito
For Edge:
-InPrivate
For Notepad++:
Path: C:\Program Files\Notepad++\notepad++.exe
TBox Send Keys:
Pass the keyboard commands to the application.
→ input
→ Short keys

Sendkeys Function:
{SENDKEYS[Key]}

Ctrl → ^
Alt → %
Shift → +
Enter → {ENTER} (Double quotes)
{SENDKEYS["{ENTER}"]}

Tab → {TAB}
{SENDKEYS["{TAB}"]}
Backspace → {backspace}
F1,... F12 → {f1}, {f2}.....{F12}
{SENDKEYS["{F4}"]}

Arrows → {UP}, {Right}, {Left}, {Down}

Ctrl + a ⇒ ^(a)
Buffer Operations:
TCP – Global Variable {CP[ParameterName]}, Buffers Local Variables {B[BufferName]}
Buffers is used to store the values and we can utilize those stored within testcase
Syntax: {B[BufferName]}
Types Of Buffers:
1. Static Buffer
a. We will define the BufferName as well Buffer Values using TBox Set Buffer & Action
Mode Buffer.
TBox Set Buffer:

Action Mode Buffer:

25/12/2024:
2. Partial Buffer
a. Partially store content from the Sentence. Start, End and Last
Sentence: Order Created1234
Start = Starting Index 14
End= Ending Index 17
Or
 Last = 4
Start and End Combination:

Last:

3. Dynamic Buffer
a. We store the values in Runtime
Order Created 1234
{XB[BufferName]} – Store Value {XB[OrdNum]} - Action Mode as Verify
{B[BufferName]} – To Use {B[OrdNum]}

TBox Delete Buffer:

By using standard Module we can delete specific or All Buffers.

Synchronization:
Mapping application speed with automation tool (Tosca) speed.
Default synchronization timing : 10000 ms (Dynamic)
Project->Setting->TBox->Synchronization
Default Timeout = 10K ms
Default Timeout for WaitOn =20K ms

1. Static Wait
TBox Wait, Assgin some seconds manually. Irrespective of application functionality it waits
for the time limit which we defined.
Forcefully we are stopping tosca execution at a certain time.

2. Dynamic Wait: Action Mode - WaitOn

This wait will help till the object visible in the AUT then it will perform the action. We
always define WaitOn in test step value, this includes application functionality.
Synchronization Timeout during waiton = 20000 ms (dynamic)
 If you want change the Synchronization wait without disturbing others we can use
TCP’s. Like below

Application Loading is more

TBox Wait -5000

Still loading then again 20K wait will considered still found then your step get failed.
18K
Login -Click
Next

Action Mode WaitOn – visible immediately perform action on the object but if it is
not found 50K wait if still not identify then it will fail. 40K if object found then it will
continue execution.
26/12/2024:
Cardinality:
If you want define the objects multiple times in the testcase we are going to use it
Cardinality.
Default value is 0-1
 We can change it to 0-2 or N then object will be visible multiple times in the
testcase

Second Way to increase Objects in the Testcase:

In the testcase copy the object and past on the test step additional object will be added to
teststep.

ExplicitName:
It is one of the Configuration Parameter. If there multiple objects are there with same
properties then you want to click on the 3 object then we can declare the Explicit Name.
rd

ExplicitName = True
Or

We can edit the test step object value as index number

DATE Operations:
dd.MM.yyyy, dd/MM/yyyy…………
{DATE}

Default Date Format is dd.MM.yyyy

M – Month
m-Minutes
d-Day
y-Year
If you want to change the Date Format then we can add TCP within the testcase:

{Date[BaseDate][Offset][Format]}
[] -> Today’s Date
[Offset]-> Validation + or – from date
Day->d
Month->M
Years->y
[Foramt]-> if this is blant then default format is dd.MM.yyyy or else you can define any
format MM/dd/yyyy or dd/MM/yyyy….etc.

27/12/2024:
Requirement : we have to add 1 day to the current date.
Syntax: {Date[][+1d][]}
Different Types of Date Formats:
—-------------------------------------------

{DATE[][][]} ⇒ 27.12.2024 (dd.MM.yyyy)

{DATE[][][d]} ⇒ 27-12-2024'
{DATE[][][dd]} ⇒ 27
{DATE[][][ddd]} ⇒ Fri'

{DATE[][][dddd]} ⇒ Friday

{DATE[][][ddddd]} ⇒ Friday

{DATE[][][M]} ⇒ 27 December
{DATE[][][MM]} ⇒ 12
{DATE[][][MMM]} ⇒ Dec
{DATE[][][MMMM]} ⇒ December
{DATE[][][MMMMM]} ⇒ December

{DATE[][][y]} ⇒ December, 2024

{DATE[][][yy]} ⇒ 24
{DATE[][][yyy]} ⇒ 2024
{DATE[][][yyyy]} ⇒ 2024

{DATE[][][ddd dd MMM]} ⇒ Fri 27 Dec

{DATE[][][ddd, MMM dd, yyy]} ⇒ Fri, Dec 27, 2024

{DATE[][][dd MMM `yy dddd]}

{DATE[][][dd MMM ‘yy dddd]} ⇒ 27 Dec ‘24 Friday

Test Configuration Parameter:
—-----------------------------------------

Overwrite a project level settings Default ⇒ dd.MM.yyyy

TargetDateFormat ⇒ MM/dd/yyyy

Time:

—----

12 hrs, 24 hrs

HH:mm ⇒ {TIME} ⇒ 24 hrs format ⇒ 21:00

h:mm tt ⇒ {TIME} ⇒ modify time format project level

Test COnfiguration Parameter:

—----------------------------------------

TargetTimeFormat = h:mm tt ⇒ 9:00 PM

Data and Time:

—-------------------

{DATETIME} ⇒ yyyyMMddHHmmss
 ⇒ 20240122210346'

TCP⇒ TargetDateAndTimeFormat ⇒
Day

===

{DAY} ⇒ 22
{ADAY} ⇒ Mon
{LDAY} ⇒ Monday

Month

=====

{MONTH} ⇒1
{AMONTH} ⇒ Jan
{LMONTH} ⇒ January
{MONTHFIRST} ⇒ 01.01.2024
{MONTHLAST} ⇒ 31.01.2024

Year:

====

{YEAR} ⇒ 24

Radom Numbers:
Generate Random numbers, this will generate only numeric values.

{RND[Digits]} = {RND[4]} – 4 digits

{RND[Start][End]} = {RND[1][9]} – Result will be between those two numbers
Min – 1
Max -18
The maximum number of digits for the generated number is 18.
RandomText:
It generates values which is having alphanumeric(include upper and lower)

{RANDOMTEXT[No.of digits]}

{RandomText[4]}
Min = 1
Max = 1024
Maximum character accepting for this method is 1024 characters

Regular Expression:
Verify the target string is having a specific format.

{REGEX["Expressions"]}

Bike Number:

TS01AB9876

{REGEX["[A-Z]{2}[0-9]{2}[A-Z]{2}[0-9]{4}"]} - Verify is action mode

Random Regular Expression:

This method is used to generate the input data in the combination.
Syntax: {RANDOMREGEX["Expression"]}

[A-Z] – Capital Letters and [a-z] – Small letters and [0-9] - digits

Example: {RANDOMREGEX["[A-Z]{2}[0-9]{2}[A-Z]{2}[0-9]{4}"]}

RTB’s – Rusable Test Step Blocks.

Creating a block for the No. Of. Test steps which we are going to be used in n of.
Testcases.
Note: When there is a requirement to use multiple times then only create the RTB’s
1. Time saving
2. All Team members will utilze
3. One time if you change in the RTB then it will reflected to others as well
Library:
If you want to create any RTB must should create the Library folder then only it is allowed to
create the RTB.
Note: Only one time is allowed to create Library folder under any folder within the
Testcase.
RTB: Within the library create n no.of RTBs.

1. Drag/drop Module into RTB.

2. Copy & Past existing script(Test step) development
3. Drag/ & Drop existing script(Test step) development

Business Parameters:

—---------------------------

Enter User input directly in the test case reference folder.

we always create these business parameters only in RTB.

{PL[Parameter Name]}

PL→ Parameter list

RTB for Launch Application:

For This Launch application we have parameterized URL
{PL[URL]}

30/12/2024:
RTB TCP TCD Buffers
Libraries Testcase F or sub TestSheets Local with testcase
BP – {PL[PN]} {CP[PN]} {XL[AN]} {B[BN]}

{Click} – Mouse moments will visible

X – Direct action
RTB Testcase Process:

Create Reusable Blocks

 First create Library Folder
Note: Create library under testcase folder anyother folder(Only once in folder)
 Create Reusable test steps blocks(RTB)
Note: Create only under Library Folder
RTB Development:
 Drag/Drop Modules to RTB
 Module Testcase Test Step
 Modules RTB Block Test Step

 Copy & Past existing script(Test step) development

 Drag/ & Drop existing script(Test step) development

RTB to Testcase:
 Once we done with RTB Development
 Drag/Drop to particular RTB into Testcase

Modification in RTB and Reference Folder:

 Comeback to RTB then Do the modifications and it will reflected to other all the
places where we have used it.
If you want see the Test steps withing the Testcase of RTB then we can goto Testcase
menu and Click on Show Test Step Details
Resolve Reference:
If you want to disconnect from RTB to Reference RTB then you choose this Resolve
reference from Testcase.

{PL[PN]}
Conditional and Looping Statements:
Conditional Statement:
Compare the two things then we are going to use it this IF Condition. IF statement is an acting
test step. It will work based on True or False.

IF Condition True or False

Syntax:
 IF
{
Condition (True or False)
Then – True
Statement
Else – False
Statement
}
Test steps:

True Output:
False Output:

Application Level Conditional Statement:

31/12/2024:
Looping Statements:
While Loop:
 This is also acting like test steps
 This Loop will continue until condition gets false
 Maximum 30 (Default) -> Modify upto 100
Note: Only Condition will be verified first then Loop will be repeated.
Syntax:
While Statement
Condition (True or False)
Loop - True
Statement
If Condition False then Loop will be terminated.
Scenario:
Assign Some Value = 1
TBox Set Buffer
Start (BN) = 1(BV)
No.Iterations(BN) = 4(BV)
While Statement
Condition {B[Start]}>={B[No.Iterations]}
Loop - True
TBox Set Buffer
Increase Start +1

Tosca Screenshot – True(Positive Sceanrios):

Tosca Screenshot – True(Negative Sceanrios):

Assignment:
Select the Radio Buttons until it gets completed count.

DO Loop:
  This is also acting like test steps
 This Loop will continue until condition gets false
 Maximum 30 (Default) -> Modify upto 100
Note: Loop will be executed first then Only Condition will be verified.
Syntax:
Do Statement
Loop - True
Statement
Condition (True or False)

If Condition False then Loop will be terminated.

Scenario:
Assign Some Value = 1
TBox Set Buffer
Start (BN) = 1(BV)
No.Iterations(BN) = 4(BV)
While Statement
Condition {B[Start]}>={B[No.Iterations]}
Loop - True
TBox Set Buffer
Increase Start +1

Example Of Positive Scenario:

Output:
Negative Scenario:

Output:

Repetition: It is like a For Loop

Simply we can define the number of time that particular folder should be repeated
specified times.
Define in 2 ways:
 Repetition column to the Testcase
 You can define in the test step folder level
 Repetition Method = {Repetition}
Assignmet:
Try to complete the 5 Registrations in the Demowebshop portal.
Open URL
Registartion
02/02/25:
TCD: Test Case Design
This is one of the Test Data Maintain process.
TCD-Manual
TCD_Automatic
Record Data Driven Test Data
Excel file
TDM/ TDS(Test Data Services)

TCD for now, Only used to update the data from our end.
EmailID: xyz@gmail.com
Hierarchy:
TCD Folder

Test sheet
Test sheet Level Instances (No. of Testcases)
Attributes -> FieldName(UserName)
Attribute Level Instances Field Values(abc@gmail.com)
TCD Folder Structure:
Business Relevant - Yes/No/Result
For All Attribute Level folder are holding default value is Yes

=====Business Relevant - No

=====BR = Yes

======BR = Result

To Add Attrivutes in TCD there are 3 ways to create

 Manually create the Attributes under Test Sheet
 Drag and Drop Madules into the Test Sheet
 Drag and Drop Cutomized test steps into Test Sheet
TCd tab → toggle character, toggle position
→ F7
Instance Level validations:
Character Property is allow these changes:
EmailID = abc@gmail.com = Valid = Straight Through
fkdjlajfdlk@gmail.com = Valid = Not Straight Through
Kdajlfkjdalfjalsd = InValid

Position Property:
EmailID = 100 Characters
1. – 100 = Boudary Values
2 - 99 = Inner Values

Test Data Generation Techniques:

 All Combination
 Pairewise
 Linear
 Orthogonal
All Combinations:
A (1,2,3) B (1,2,3) = cube related results will be updated and it should cover all
combination of data.
Orthogonal:
No duplicates will allowed and also less number of combinations.

Pairwise:
It do the pair of each attr level instances another attribute level instances
some time may you will get same count test sheet level instances for
AllCombinations and pairwise
A,b,c ⇒ 1,2
(a,1)(a,2) (b,1)(b,2) (c,1)(c,2)

Linear Expansion:
Create at least one straight through instance for each attribute.
It always take the combinations straight through with valid and Invalid
 ERROR: The linear expansion can not be performed
A StraightThrough-Instance can not be generated because the following Business relevant
StructureElement(s) contain(s) no StraightThrough-Instances.

Combinations:
(a,3) → Straight through
(b,3) → Valid, Straight through
(c,3) → InValid, Straight through
(a,1) → Straight through, Invalid
(a,2) → Straight through, Valid

WorkFlow:
1. create Test Data (Manual And Automatic)

2. TCD

1. Manual

2. Automatic

3. create Test sheet

Attributes

1. Create Attr and select Types (Business Relevant)

 2. attr_Instances and its Types,

Instance Character, instance position

Instances

3. Test sheet level instances→ different sets of data.

4. Test Case section

1. create Test Case and follow Recommended workflow

( Pre-condition, process, post condition).

2. Test DATA

→ Map Test sheet into testcase.

No, (Testcase accepts only one set of data)

→ Convert Test Case into Template

Right click on test case → click on convert to template.

⇒ Templet Will accept different combinations of data.

Note: We can’t execute templates, this is only for mapping purposes.

5. Test Sheet Mapping onto Template

1. Drag/drop Test Sheet into Template.

2. verify Schema name is reflected in properties tab

3. verify each attr is mapped with test step value col level as

Syntax {XL[AttrName]}.

4. If not mapped Attr automatically then we need to map Manually.

⇒ Drag/drop Test sheet Attribute into Teststep value col in template.

Then It will create a syntax that is {XL[ attr name]}

6. Generate Template Instances Activities:

1. check the template

Right click on template and select check template

 -> If Errors is there in mapping, fix the Errors

-> If no Errors

2. generate template instances

Right click on template ⇒ click on 3 dots down arrow ⇒ Create Template instances.

3. It will create one TemplateInstance Folder

⇒ It will generate test cases based on a data defined Test sheet.

⇒ Each test case with format which is defined in the template.

7. execute TemplateInstance instance folder using Scratchbook and execution list.

→ Drag/drop Template Instance folder to execution list folder and do Run.

TCD: Class:
Similar to the RTB. Keep the reusable attr and attr level instances into class.
There is no limit
1. Right click on TCD folder → Click on Class
2. Drag/drop Module into TCD Folder → Class