QTP

Checkpoint is basically a point in the test which validates for truthfulness of specific things in the AUT. There are different types of checkpoints depending on the type of data that needs to be tested in the AUT. It can be text, image/bitmap, attributes, XML etc…. A checkpoint verifies that expected information is displayed in your application while the test is running. Check point can be customized as per the user need and it’s very helpful during testing. Quick Test professional support wide variety of […]

Recovery scenario settings enable you to specify how a business component recovers from unexpected events and errors during a run session or during execution Trigger: Trigger is nothing but the cause for initiating the recovery scenario. It could be any popup window, any test error, particular state of an object or any application error. Action: Action defines what needs to be done if scenario has been triggered. It can consist of a mouse/keyboard event, close application, call a recovery function defined in library file or […]

The objects in the application are dynamic in nature and need special handling to identify the object. The best example would be of clicking a link which changes according to the user of the application, Ex. Logout

QTP uses its object repository to refer to objects present in your test and which have been recorded, if you wish to use objects that were not recorded and are not present in your object repository then we use descriptive programming, where QTP does not refer to object repository but the property name and value are mentioned in the code itself for QTP to use it for e.g this is not Desc. prog. Browser(“Mercury Tours”).Page(“Mercury Tours”).WebEdit(“username”) This is desc prog. Browser(“Title:=Mercury Tours”).Page(“Title:=Mercury Tours”).WebEdit(“Name:=Author”, “Index:=3”).Set “Mahesh” […]

By descriptive programming