It is very intresting to me that QTP 10.0 & IE 8 have had a good working relation. I have always considered the fact of irregular behaviour between the two, predominantly towards IE8. Now that it works fine for you lets load the gun.
1. Have you tried to use the Wait statement before the checkpoint ? [ This isint advisable but you can use this to verify that it is a matter of "time" which is causing the issue ]
If it was a mere wait which is required to sync the application interface then you can look for a property on the browser/page which talks about being busy. Then you can form the logic as,
"Loop until the property achieves the busy state and end it after that or if it reaches a max of 30 iterations".
You will learn about it more if you spend sometime searching this forum. A thread was answered by me and then jsknight wrote further about it.[ thats a clue to start with...good luck buddy]
1. Have you tried to use the Wait statement before the checkpoint ? [ This isint advisable but you can use this to verify that it is a matter of "time" which is causing the issue ]
If it was a mere wait which is required to sync the application interface then you can look for a property on the browser/page which talks about being busy. Then you can form the logic as,
"Loop until the property achieves the busy state and end it after that or if it reaches a max of 30 iterations".
You will learn about it more if you spend sometime searching this forum. A thread was answered by me and then jsknight wrote further about it.[ thats a clue to start with...good luck buddy]
Basanth
Give a fish to a man and you feed him for a day..Teach a man how to fish and you feed him for life.
Give a fish to a man and you feed him for a day..Teach a man how to fish and you feed him for life.
