Winrunner Question 73: How do you create parameterize SQL commands?

How do you create parameterize SQL commands?

• 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:

SELECT Flights.Departure, Flights.Flight_Number, Flights.Day_Of_Week FROM Flights Flights WHERE (Flights.Departure=?) AND (Flights.Day_Of_Week=?)

     SELECT defines the columns to include in the query.
     FROM specifies the path of the database.
WHERE (optional) specifies the conditions, or filters to use in the query.
Departure is the parameter that represents the departure point of a flight.
Day_Of_Week is the parameter that represents the day of the week of a flight.

• When creating a database checkpoint, you insert a db_check statement into your test script. When you parameterize the SQL statement in your checkpoint, the db_check function has a fourth, optional, argument: the parameter_array argument. A statement similar to the following is inserted into your test script:

db_check("list1.cdl", "dbvf1", NO_LIMIT, dbvf1_params);

The parameter_array argument will contain the values to substitute for the parameters in the parameterized checkpoint.

Winrunner Question 72: How do you parameterize database check points?

How do you parameterize database check points?
When you create a standard database checkpoint using ODBC (Microsoft Query), you can add parameters to an SQL statement to parameterize the checkpoint. This is useful if you want to create a database checkpoint with a query in which the SQL statement defining your query changes

Winrunner Question 71: How do you convert a database file to a text file?

How do you convert a database file to a text file?
You can use Data Junction to create a conversion file which converts a database to a target text file.

Winrunner Question 70: How do you record a data driven test?

How do you record a data driven test?
We can create a data-driven testing using data from a flat file, data table or a database.

• Using Flat File: we actually store the data to be used in a required format in the file. We access the file using the File manipulation commands, reads data from the file and assign the variables with data.


• Data Table: It is an excel file. We can store test data in these files and manipulate them. We use the ‘ddt_*’ functions to manipulate data in the data table.


• Database: we store test data in the database and access these data using ‘db_*’ functions.

Winrunner Question 69: How do you create ODBC query?

How do you create ODBC query?
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 Question 68: How do you handle ActiveX and Visual basic objects?

How do you handle ActiveX and Visual basic objects?
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 Question 67: How do you modify the expected results of a GUI checkpoint?

How do you modify the expected results of a GUI checkpoint?
We can modify the expected results of a GUI checkpoint be running the script containing the checkpoint in the update mode.

Winrunner Question 66: How do you edit the expected value of an object?

How do you edit the expected value of an object?
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.

Winrunner Question 65: How do you edit checklist file and when do you need to edit the checklist file?

How do you edit checklist file and when do you need to edit the checklist file?
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 or a shared one. Select the checklist file, click OK which opens up the window to edit the properties of the objects.

Winrunner Question 64: What do you verify with the sync point for screen area and what command it generates, explain syntax?

What do you verify with the sync point for screen area and what command it generates, explain syntax?

• For screen area verification we actually capture the screen area into a bitmap and verify the application screen area with the bitmap file during execution

Syntax: obj_wait_bitmap(object, image, time, x, y, width, height);

Winrunner Question 63: What do you verify with the sync point for object/window bitmap and what command it generates, explain syntax?

What do you verify with the sync point for object/window bitmap and what command it generates, explain syntax?

• You can create a bitmap synchronization point that waits for the bitmap of an object or a window to appear in the application being tested.


• During a test run, WinRunner suspends test execution until the specified bitmap is redrawn, and then compares the current bitmap with the expected one captured earlier. If the bitmaps match, then WinRunner continues the test.

Syntax:
obj_wait_bitmap ( object, image, time );
win_wait_bitmap ( window, image, time );

Winrunner Question 62: What do you verify with the sync point for object/window property and what command it generates, explain syntax?

What do you verify with the sync point for object/window property and what command it generates, explain syntax?

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


• You can a synchronization point that instructs WinRunner to wait for a specified object or window to appear. For example, you can tell WinRunner to wait for a window to open before performing an operation within that window, or you may want WinRunner to wait for an object to appear in order to perform an operation on that object.


• You use the obj_exists function to create an object synchronization point, and you use the win_exists function to create a window synchronization point. These functions have the following syntax:

Syntax:
obj_exists ( object [, time ] );
win_exists ( window [, time ] );