WR Testing Tutorial

WR History
WR Integrations

WR Testing

WR Testing Process
WR Recording
WR CheckPoints
WR FunctionGen
WRGUI Spy
WR GUI Map
WR GUI Configuration
WR V User Object
WR Data Driven Test
WR Parameterization
WR TSL
Learn More...

WR Examples(Script)

WR Script1
WR Script2
WR Script3
WR Script4
WR Script5
WR Script6
WR Script7
WR Script8
WR Script9
WR Script10
WR Examples More...

WR Interview Q&As
WR Q&As1
WR Q&As2
WR Q&As3
WR Q&As4
WR Q&As5
WR Q&As6
WR Q&As7
WR Q&As8
WR Q&As9
WR Q&As10
WR Q&As11
WR Q&As12
WR Q&As13
WR Q&As14
WR Q&As15
WR Q&As16
WR Q&As17
WR Q&As18
WR Q&As19
WR Q&As20
WR Q&As More...

WR FAQ(mp3)
Listen WR FAQ1
Listen WR FAQ2
Listen WR FAQ3
Listen WR FAQ4
Listen WR FAQ5
Listen WR FAQ6
Listen WR FAQ7
Listen WR FAQ8
Listen WR FAQ9
Listen WR FAQ10
Listern More on WR
pixels

THE LARGEST SOFTWARE TESTING SITE ON THE NET

KabInfo.Net  - Full Testing Tutorials - All Free

 

At KabInfo.Net you will find all the Manual and Automation Testing tutorials,
from basic Testing Definition and Testing Types,Testing Methodologies to advanced  Automation Tools like, WinRunner, LoadRunner and a Test Management Tool like TestDirector.

KabInfo.Net - The Largest Enterprise Application Testers site on the Net

Best Tester:- who gets the most bugs fixed :: Smart Tester:- Balances between listening and implementing

:::

KabInfo.Net                                     

 

1)       What do you verify with the bitmap checkpoint for screen area and what command it generates, explain syntax?

a)        You can define any rectangular area of the screen and capture it as a bitmap for comparison. The area can be any size: it can be part of a single window, or it can intersect several windows. The rectangle is identified by the coordinates of its upper left and lower right corners, relative to the upper left corner of the window in which the area is located. If the area intersects several windows or is part of a window with no title (for example, a popup window), its coordinates are relative to the entire screen (the root window).

 b)       To capture an area of the screen as a bitmap:

                                                                i.      Choose Create > Bitmap Checkpoint > For Screen Area or click the Bitmap Checkpoint for Screen Area button. Alternatively, if you are recording in Analog mode, press the CHECK BITMAP OF SCREEN AREA softkey. The WinRunner window is minimized, the mouse pointer becomes a crosshairs pointer, and a help window opens.

                                                              ii.      Mark the area to be captured: press the left mouse button and drag the mouse pointer until a rectangle encloses the area; then release the mouse button.

                                                            iii.      Press the right mouse button to complete the operation. WinRunner captures the area and generates a win_check_bitmap statement in your script.

                                                            iv.      The win_check_bitmap statement for an area of the screen has the following syntax:

   win_check_bitmap ( window, bitmap, time, x, y, width, height );

 

 2)       What do you verify with the database checkpoint default and what command it generates, explain syntax?

a)        By adding runtime database record checkpoints you can compare the information in your application during a test run with the corresponding record in your database. By adding standard database checkpoints to your test scripts, you can check the contents of databases in different versions of your application.

b)        When you create database checkpoints, you define a query on your database, and your database checkpoint checks the values contained in the result set. The result set is set of values retrieved from the results of the query.

c)        You can create runtime database record checkpoints in order to compare the values displayed in your application during the test run with the corresponding values in the database. If the comparison does not meet the success criteria you

d)        specify for the checkpoint, the checkpoint fails. You can define a successful runtime database record checkpoint as one where one or more matching records were found, exactly one matching record was found, or where no matching records are found.

 

e)        You can create standard database checkpoints to compare the current values of the properties of the result set during the test run to the expected values captured during recording or otherwise set before the test run. If the expected results and the current results do not match, the database checkpoint fails. Standard database checkpoints are useful when the expected results can be established before the test run.

 Syntax: db_check(<checklist_file>, <expected_restult>); 

f)        You can add a runtime database record checkpoint to your test in order to compare information that appears in your application during a test run with the current value(s) in the corresponding record(s) in your database. You add runtime database record checkpoints by running the Runtime Record Checkpoint wizard. When you are finished, the wizard inserts the appropriate db_record_check statement into your script.

 Syntax:

db_record_check(ChecklistFileName,SuccessConditions,RecordNumber );

ChecklistFileName              A file created by WinRunner and saved in the test's checklist folder. The file contains information about the data to be captured during the test run and its corresponding field in the database. The file is created based on the information entered in the Runtime Record Verification wizard.

SuccessConditions            Contains one of the following values:

1.        DVR_ONE_OR_MORE_MATCH - The checkpoint passes if one or more matching database records are found.

2.        DVR_ONE_MATCH - The checkpoint passes if exactly one matching database record is found.

3.        DVR_NO_MATCH - The checkpoint passes if no matching database records are found.

RecordNumber An out parameter returning the number of records in the database.

 

KabInfo.Net                                     

 

:::

Where to Start

What does a Software Test Engineer have to know? What will the future bring?

KabInfo.Net will try to answer this, and help you become a professional Software Test Engineer, well prepared for the future.

Before you study the tutorials, Read this introduction.

:::

Quick and Easy Learning

Because time is valuable, we deliver quick and easy learning. At KabInfo.Net, you can study everything you need to learn, in an accessible and handy format.

                        "No One Is Great, And Every One Is GREAT"

K.A.Babu (2004)

:::

Testing Joke

Tester : "I Delivered a 100% Bug Free Product!"

:::

KabInfo.Net - Testing School is for self training only. We do not warrant the correctness of the content. The risk of using it remains entirely with the user. While using this site, you agree to have read and accepted our terms of use and privacy policy.

Copyright 2004 . All Rights Reserved.

Logo Courtesy - Venkat Battu

KAB SEARCH

                     About KabInfo.Net
KabInfo downloads

REFERENCES
Test Case Doc
Test Plan Doc
B.R.S/B.R.D
Fun.Spec/Fun.Doc
System Req. Spec. Design Doc
Bug Report
Check List
Test Discussions Doc
.....Other Docs

Listen Testing


After A Bug Is Found
Integreation Testing
Quality
Software Life Cycle
Test Engineer
Types Of Testing
Unit Testing
Testing Concepts
WinRunner
QTP
More MP3s soon...
Q & A Section

Teting
Manual Testing
Automation
WinRunner
LoadRunner
TestDirector
Q.T.P
SQL
CERTIFICATION(S)

CSQA Certification
CSTE Certification
CSPM Certification
VALIDATION
Validate Date
Validate ComboBox
Validate Traingle
Validate Login   Validate E-Mail
Freshers
Seeking S/W Testing Job?

 
 

pixels  

Best Tester???