| || |
In the application that I am testing, I record multiple pages for different screens.
At times, during navigation, ETester does not wait for the page to load up completely and starts executing the code in "afterplay" and hence my script fails.
I have set option 'WaitForNavsOnBrowserIdle' to True, but still this problem persists.
Is there some kind of WatchObject(like in QTP) in ETester?
Your help is much appreciated.
Not that I recall. In the past I have gotten around this issue by recording an extra event on the page and then executing the code based on that trigger. The work around is based on the fact that e-Tester will wait for the browser complete to occur before executing any events.
it is really like that "The work around is based on the fact that e-Tester will wait for the browser complete to occur before executing any events"