What do we verify with the database check point custom and what command it generates, explain syntax?
> When you create a custom check on a database, you create a standard database checkpoint in which you can specify which properties to check on a result set.
> You can create a custom check on a database in order to :
* check the contents of part or the entire result set
* edit the expected results of the contents of the result set
* count the rows in the result set
* count the columns in the result set
> You can create a custom check on a database using ODBC, Microsoft Query or Data Junction. Reply
How do we handle dynamically changing area of the window in the bitmap checkpoints?
The difference between bitmaps option in the Run Tab of the general options defines the minimum number of pixels that constitute a bitmap mismatch .Reply
What do you verify with the bitmap checkpoint for screen area and what command it generates, explain syntax?
> We 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).
> To capture an area of the screen as a bitmap:
A. 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.
B. 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.
C. Press the right mouse button to complete the operation. WinRunner captures the area and generates a win_check_bitmap statement in your script.
D. 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 );
What do you verify with the bitmap check point for object/window and what command it generates, explain syntax?
> You can check an object, a window, or an area of a screen in our application as a bitmap. While creating a test, we indicate what we want to check. WinRunner captures the specified bitmap, stores it in the expected results folder (exp) of the test, and inserts a checkpoint in the test script. When we run the test, WinRunner compares the bitmap currently displayed in the application being tested with the expected bitmap stored earlier. In the event of a mismatch, WinRunner captures the current actual bitmap and generates a difference bitmap. By comparing the three bitmaps (expected, actual, and difference), we can identify the nature of the discrepancy.
* When working in Context Sensitive mode, We can capture a bitmap of a window, object, or of a specified area of a screen. WinRunner inserts a check point i the test script in the form of either a win_check_bitmap or obj_check_bitmap statement.
> Note that when you record a test in Analog mode, We should press the CHECK BITMAP OF WINDOW softkey or the CHECK BITMAP OF SCREEN AREA softkey to create a bitmap checkpoint. This prevents WinRunner from recording extraneous mouse movements. If we are programming a test, you can also use the Analog function check_window to check a bitmap.
> To capture a window or object as a bitmap:
A. Choose Create - Bitmap Checkpoint - For Object/Window or click the Bitmap Checkpoint for Object/Window button on the User toolbar. Alternatively, if you are recording in Analog mode, press the CHECK BITMAP OF OBJECT/WINDOW softkey. The WinRunner window is minimized, the mouse pointer becomes a pointing hand, and a help window opens.
B. Point to the object or window and click it. WinRunner captures the bitmap and generates a win_check_bitmap or obj_check_bitmap statement in the script. The TSL statement generated for a window bitmap has the following syntax: win_check_bitmap ( object, bitmap, time );
C. For an object bitmap, the syntax is: obj_check_bitmap ( object, bitmap, time );
D. For example, when you click the title bar of the main window of the Flight Reservation application, the resulting statement might be: win_check_bitmap ("Flight Reservation", "Img2", 1);
E. However, if you click the Date of Flight box in the same window, the statement might be: obj_check_bitmap ("Date of Flight:", "Img1", 1);
Syntax: obj_check_bitmap ( object, bitmap, time [, x, y, width, height] ); Reply
What information is contained in the checklist file and in which file expected results are stored?
The checklist file contains information about the objects and the properties of the object we are verifying.
The gui*.chk file contains the expected results which is stored in the exp folder.Reply
What do we verify with the GUI checkpoint for multiple objects and what command it generates, explain syntax?
To create a GUI checkpoint for two or more objects :
> Choose Create GUI Checkpoint For Multiple Objects or click the GUI Checkpoint for Multiple Objects button on the User toolbar. If we are recording in Analog mode, press the CHECK GUI FOR MULTIPLE OBJECTS softkey in order to avoid extraneous mouse movements. The Create GUI Checkpoint dialog box opens.
> Click the Add button. The mouse pointer becomes a pointing hand and a help window opens.
> To add an object, click it once. If we click a window title bar or menu bar, a help window prompts we to check all the objects in the window.
> The pointing hand remains active. We can continue to choose objects by repeating step 3 above for each object you want to check.
> Click the right mouse button to stop the selection process and to restore the mouse pointer to its original shape. The Create GUI Checkpoint dialog box reopens.
> The Objects pane contains the name of the window and objects included in the GUI checkpoint. To specify which objects to check, click an object name in the Objects pane. The Properties pane lists all the properties of the object. The default properties are selected.
* To edit the expected value of a property, first select it. Next, either click the Edit Expected Value button, or double-click the value in the Expected Value column to edit it.
* To add a check in which we specify arguments, first select the property for which we want to specify arguments. Next, either click the Specify Arguments button, or double-click in the Arguments column. Note that if an ellipsis appears in the Arguments column, then we must specify arguments for a check on this property. (We do not need to specify arguments if a default argument is specified.) When checking standard objects, We only specify arguments for certain properties of edit and static text objects. We also specify arguments for checks on certain properties of nonstandard objects.
* To change the viewing options for the properties of an object, use the Show Properties buttons.
> To save the checklist and close the Create GUI Checkpoint dialog box, click OK. WinRunner captures the current property values of the selected GUI objects and stores it in the expected results folder. A win_check_gui statement is inserted in the test script.
Syntax : win_check_gui ( window, checklist, expected_results_file, time );
obj_check_gui ( object, checklist, expected results file, time ); Reply
How do we view the contents of the GUI map?
GUI Map editor displays the content of a GUI Map. We can invoke GUI Map Editor from the Tools Menu in WinRunner. The GUI Map Editor displays the various GUI Map files created and the windows and objects learned in to them with their logical name and physical description. Reply
What is the different between GUI map and GUI map files?
The GUI map is actually the sum of one or more GUI map files. There are two modes for organizing GUI map files :
> Global GUI Map file: a single GUI Map file for the entire application
> GUI Map File per Test: WinRunner automatically creates a GUI Map file for each test created.
GUI Map file is a file which contains the windows and the objects learned by the WinRunner with its logical name and their physical description. Reply
If the object does not have a name then what will be the logical name?
If the object does not have a name then the logical name could be the attached text.Reply
What do you mean by the logical name of the object?????