Tutorial-8 How to insert Synchronization Point to pause a test in QTP
How to insert Synchronization Point to pause a test in QTP
This short tutorial guides you to the process of inserting a Synchronization Point in a test in QTP.
Step 1: Start the recording of the test.
Step 2:
Display the screen of the application, which contains the object for which we want to insert a synchronization point.
Step 3:
In QTP choose“Insert” > “Step” > “Synchronization Point”. The mouse pointer will change its shape to a pointing hand.
Step 4:
Click the object in the application for which we want to insert the synchronization point.
If the location clicked by us is associated with more than one object in the application, the “Object Selection Synchronization Point” dialog box shall open.
Step 5:
Select the object for which synchronization point needs to be inserted, then click “OK”.
The “Add Synchronization Point” dialog box shall open.
Step 6:
The Property name list contains the test object properties associated with the object.
Select the Property name, which is required to be used for the synchronization point.
Step 7:
Enter the property value for which we want that QTP to wait prior to moving on to the next step in the test.
Step 8:
Enter the synchronization point timeout (in milliseconds) after which we want that QTP to move ahead to the next step, even if the specified property value had not been achieved.
Step 9:
Click “OK”. A “WaitProperty” step gets added to our test.
For instance when we want to insert a synchronization point for the “Update” button, it can appear like the following:
Window(“Flights”).WinButton(“Update”).WaitProperty “enabled”, 1, 2000
Many More Tutorials on HP QTP 11.0
An expert on R&D, Online Training and Publishing. He is M.Tech. (Honours) and is a part of the STG team since inception.
Hi Everyone,
My company is about to start automating an application developed in .Net and WPF based controls. Can anyone please suggest an appropriate automation tool to test WPF controls?
Thanks & Best Regards,
Rajneesh
I can suggest you to try Froglogic SQUISH which we are using currently to identify custom WPF controls and till now its working fine for us.
Let us know in case you want to know any anything about SQUISH.
Cheerz,
Ian