Are you specifying a wait time in the run browser settings as shown below? If yes, what number are you specifying?
If not, can you click on Tools -> Current project properties and see what value is given here:
Hi djadhav.
I have attached a screenshot of the keyword test. The line that is causing the delay is outlined.
As for a log file, there really isn't one. This is working correctly, it is just taking over a minute for the test to navigate to the login window, but the window is displaying on the screen awaiting the password while the test states that it is navigating to the window. I don't understand why there is a delay navigating when the window is up and waiting for the password.
Thank you for your time.
Dave.
Looking at the screenshot one thing that immediately comes to notice that possibly in your namemapping, the windows security dialog object is a child of the browser object. This would interfere in detecting the object. Can you try after namemapping the dlgWindowsSecurity2 as an independent object.
That piece is running well. It's actually the Run Browser part of the test prior to the dlgWidnowsSecurity2 that is taking unusually long.
Thank you for the thought. It's much appreciated!
Are you specifying a wait time in the run browser settings as shown below? If yes, what number are you specifying?
If not, can you click on Tools -> Current project properties and see what value is given here:
Yes! That was it! You know, I saw that setting earlier on and thought it would impact the timeout and cause the test to stop. I set it to 10000 and it went much quicker. Thank you djadhav. Well done!
Dave.
