Interview Questions

Test Recorder about Control Points - Check Points

Mercury WinRunner FAQ

(Continued from previous question...)

Test Recorder about Control Points - Check Points

1. Any checkpoints should not be a component of X & Y Co-ordinate dependant. In practical terms if there is a Check point that is defined on X,Y Parameters then the usability of the control point wouldn't make any sense for the application to test. The following are some of the criteria which denotes the do's and don't's of checkpoints.

S.No Check Point Include Exclude
1 Text Check Capture Text, Position of the Text, Font & Font Size, Text area,
2 Bitmap Check only the picture Window or Screen that holds the picture, x-y co-ordinates,
3 Web Check URL Check, orphan page Avoid any text validation

2. As a case study, the WinRunner automation tool is mentioned here as examples for creating check points. Usage of OBJ_CHECK_INFO or WIN_CHECK_INFO can be avoided and inculcate the idea of creating always the GUI Check point with Multiple Property. The advantages are to identify every small object with its clause, properties and its relativity with the previous versions. This not only enables the Regression comparisons but also it gives you the flexibility of defining the GUI Checks in all Physical state of the Object.

(Continued on next question...)

Other Interview Questions