WR Testing Tutorial

WR History
WR Integrations

WR Testing

WR Testing Process
WR Recording
WR CheckPoints
WR FunctionGen
WR GUI Configuration
WR V User Object
WR Data Driven Test
WR Parameterization
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


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




1)       Explain the following commands:

a)        db_connect

                                                               i.      to connect to a database

db_connect(<session_name>, <connection_string>);

 b)        db_execute_query

                                                               i.      to execute a query

db_execute_query ( session_name, SQL, record_number );

record_number  is the out value.

 c)        db_get_field_value

                                                               i.      returns the value of a single field in the specified row_index and column in the session_name database session.


db_get_field_value ( session_name, row_index, column );

d)        db_get_headers

                                                               i.      returns the number of column headers in a query and the content of the column headers, concatenated and delimited by tabs.

 db_get_headers ( session_name, header_count, header_content );

 e)        db_get_row

                                                               i.      returns the content of the row, concatenated and delimited by tabs.

 db_get_row ( session_name, row_index, row_content );

f)        db_write_records

                                                               i.      writes the record set into a text file delimited by tabs.

                    db_write_records ( session_name, output_file [ , headers [ , record_limit ] ] );

 g)        db_get_last_error

                                                               i.      returns the last error message of the last ODBC or Data Junction operation in the session_name database session.

 db_get_last_error ( session_name, error );

 h)       db_disconnect

                                                               i.      disconnects from the database and ends the database session.

 db_disconnect ( session_name );

 i)         db_dj_convert

                                                               i.      runs the djs_file Data Junction export file. When you run this file, the Data Junction Engine converts data from one spoke (source) to another (target). The optional parameters enable you to override the settings in the Data Junction export file.

db_dj_convert ( djs_file [ , output_file [ , headers [ , record_limit ] ] ] );


2)       What check points you will use to read and check text on the GUI and explain its syntax?

a)        You can use text checkpoints in your test scripts to read and check text in GUI objects and in areas of the screen. While creating a test you point to an object or a window containing text. WinRunner reads the text and writes a TSL statement to the test script. You may then add simple programming elements to your test scripts to verify the contents of the text.

 b)        You can use a text checkpoint to:

                                                               i.      Read text from a GUI object or window in your application, using obj_get_text and win_get_text

                                                              ii.      Search for text in an object or window, using win_find_text and obj_find_text

                                                            iii.      Move the mouse pointer to text in an object or window, using obj_move_locator_text and win_move_locator_text

                                                            iv.      Click on text in an object or window, using obj_click_on_text and win_click_on_text

 3)       Explain Get Text checkpoint from object/window with syntax?

a)        We use obj_get_text (<logical_name>, <out_text>) function to get the text from an object

b)       We use win_get_text (window, out_text [, x1, y1, x2, y2]) function to get the text from a window.

 4)       Explain Get Text checkpoint from screen area with syntax?

a)       We use win_get_text (window, out_text [, x1, y1, x2, y2]) function to get the text from a window.


 5)       Explain Get Text checkpoint from selection (web only) with syntax?

a)        Returns a text string from an object.

 web_obj_get_text (object, table_row, table_column, out_text [, text_before, text_after, index]);

                                                                i.      object      The logical name of the object.

                                                              ii.      table_row                If the object is a table, it specifies the location of the row within a table. The string is preceded by the # character.

                                                            iii.      table_column          If the object is a table, it specifies the location of the column within a table. The string is preceded by the # character.

                                                            iv.      out_text   The output variable that stores the text string.

                                                              v.      text_before             Defines the start of the search area for a particular text string.

                                                            vi.      text_after Defines the end of the search area for  a particular text string.

                                                           vii.      index       The occurrence number to locate. (The default parameter number is numbered 1).





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


                     About KabInfo.Net
KabInfo downloads

Test Case Doc
Test Plan Doc
System Req. Spec. Design Doc
Bug Report
Check List
Test Discussions Doc
.....Other Docs

Listen Testing

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

Manual Testing

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



Best Tester???