Few Good Scenarios for ATM Mechines

1.To verify ATM card Insertion
2.To verify ATM card Insertion in wrong angle
3.To verify invalid ATM card Insertion
4.To verify Language selection
5.To verify Pin entry
6.To verify invalid Pin entry
7.To verify invalid Pin entry 3 times
8.To verify Account Type selection
9.To verify Invalid Account Type selection with respectiveto inserted card
10.verify withdrawal option selection
11.verify Amount entry
12.verify Amount entry with wrong denominations(fr eg:00.999Rs)
13.verify withdrawal success operation
14.Verify operation when our entered amount is grater thanpossible balance
15.Verify operation when our entered amount is grater thanday limit
16.Verify when our ATM have lack of Amount
17.Verify when our ATM have network problem
18.Verify Current transaction No.exceeded than day limit
19.Verify operation with exceeded delay in betweenoperations in ATM
20.Verify Cancel after insert card
21.Verify Cancel after Language selection
22.Verify Cancel after Pin entry
23.Verify Cancel after Amount type selection
24.Verify Cancel after withdrawal operation
25.Verify Cancel after Amount entry
26.Verify correction of Amount during entry
27.Verify after successful transaction If customer doesn'ttake the money

QTP Life Saving Tips _1

QTP Testing Process

1. Preparation for Test Flow and Recording.
2. Recording/Scripting Test flow.
3. Enhancing the Test.
4. Debugging the Test.
5. Setup the Test inside FrameWork.
6. Running the Test.
7. Analyzing the Result.

Types of Recording

1. Context Sensitive (Based on Objects)
Window("Index Page").Dialog("Sign In User").WinButton("SignIn").Click
2. Analog (Based on Mouse Moments)
Window("Index Page").RunAnalog "Track 3"
3. Low Level (Based on Coordinates)
Window("Index Page").Dialog("Sign In User").WinButton("SignIn").Click 25,5

Object Repository

1. Local Object Repository
Action specific, can not call in other actions and tests
2. Shared Object Repository
Test Specific, can call in other actions and tests.

Object Identification

1. Normal Identification
First Mandatory Properties and then Assistive Properties until getting the unique description. If both fails QTP will user Ordinal Identifiers (Location and Index).
2. Smart Identification
If this enabled QTP will not use Ordinal Identifiers and will use Base Filter Properties and Optional Filter Properties respectively.

Two Good SQL Tricks

Actually these two things are not Tricks for SQL Masters, but for dummies like me hope this will help a lot.
1. To find the specific table name, with a part of table name we can use this Query
sp_tables '%USR%' This will give u the result of table name with "USR" word.
2. Once you got a table name to get all the details. Just use the table name in ur editor then select the table name fully and press "ALT+F1". This will give you the details about the table, its contents and options inside.

Good Day

Font Setting for QTP Scripting

Here is the best Font setting for QTP Scripting.

The need of Team Support in Testing

Do not distrub a sleeping Tester

Cool Change Request flow for a good project