The treturn and texit statements are used to stop execution of called tests. i. The treturn statement stops the current test and returns control to the calling test. ii. The texit statement stops test execution entirely, unless tests are being called from a batch test. In this case, control is returned to the main batch test. b. Both functions provide a return value for the called test. If...

You can use two types of call statements to invoke one test from another: i. A call statement invokes a test from within another test. ii. A call_close statement invokes a test from within a script and closes the test when the test is completed. iii. The call statement has the following syntax: 1. call test_name ( [ parameter1, parameter2, ...parametern ] ); iv. The call_close statement has the...

We use web_obj_text_exists function for web text checkpoints. web_obj_text_exists ( object, table_row, table_column, text_to_find [, text_before, text_after] ); object The logical name of the object to search. b. 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 #. c. table_column If the object is a table, it specifies...

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,...

You can incorporate decision-making into your test scripts using if/else or switch statements. i. An if/else statement executes a statement if a condition is true; otherwise, it executes another statement. It has the following syntax: if ( expression ) statement1; [ else statement2; ] expression is evaluated. If expression is true, statement1 is executed. If expression1 is false, statement2...

A switch statement enables WinRunner to make a decision based on an expression that can have more than two values. It has the following syntax: switch (expression ) { case case_1: statements case case_2: statements case case_n: statements default: statement(s) } b. The switch statement consecutively evaluates each case expression until one is found that equals the initial expression. If...

A TSL exception enables you to detect and respond to a specific error code returned during test execution. b. Suppose you are running a batch test on an unstable version of your application. If your application crashes, you want WinRunner to recover test execution. A TSL exception can instruct WinRunner to recover test execution by exiting the current test, restarting the application, and continuing...

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...

Synchronization compensates for inconsistencies in the performance of your application during a test run. By inserting a synchronization point in your test script, you can instruct WinRunner to suspend the test run and wait for a cue before continuing the test.b. You can a synchronization point that instructs WinRunner to wait for a specified object or window to appear. For example, you can...

A parameterized query is a query in which at least one of the fields of the WHERE clause is parameterized, i.e., the value of the field is specified by a question mark symbol ( ? ). For example, the following SQL statement is based on a query on the database in the sample Flight Reservation application: i. SELECT Flights.Departure, Flights.Flight_Number, Flights.Day_Of_Week FROM Flights Flights...

We comment a script or line of script by inserting a ‘#’ at the beginning of the line.

The steps involved in data driven testing are: i. Creating a test ii. Converting to a data-driven test and preparing a database iii. Running the test iv. Analyzing the test results.

Before creating a test, you can document information about the test in the General and Description tabs of the Test Properties dialog box. You can enter the name of the test author, the type of functionality tested, a detaileddescription of the test, and a reference to the relevant functional specifications document.

A pop-up exception Handler handles the pop-up messages that come up during the execution of the script in the AUT. TO handle this type of exception we make WinRunner learn the window and also specify a handler to the exception. It could be i. Default actions: WinRunner clicks the OK or Cancel button in the pop-up window, or presses Enter on the keyboard. To select a default handler, click the...

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.

You can use Data Junction to create a conversion file which converts a database to a target text file.

We can create ODBC query using the database checkpoint wizard. It provides with option to create an SQL file that uses an ODBC DSN to connect to the database. The SQL File will contain the connection string and the SQL statement.

WinRunner provides with add-ins for ActiveX and Visual basic objects. When loading WinRunner, select those add-ins and these add-ins provide with a set of functions to work on ActiveX and VB objects.

WinRunner has an edit checklist file option under the create menu. Select the “Edit GUI Checklist” to modify GUI checklist file and “Edit Database Checklist” to edit database checklist file. This brings up a dialog box that gives you option to select the checklist file to modify. There is also an option to select the scope of the checklist file, whether it is Test specific...

We can modify the expected value of the object by executing the script in the Update mode. We can also manually edit the gui*.chk file which contains the expected values which come under the exp folder to change the values.