Auto Wait for CMD window can't be changed
Hi there, I'm currently using an application in my tests that is not the actual SUT but helps me to perform some tasks that are needed. When clicking a certain button in the application it exec...
Forum Discussion
Hi David,
Thanks for the response.
A quick check shows that you are right, the ASynch method works on other buttons.
I have recorded a video to show the difference in execution between clicking the button and using the ASynch method:
http://screencast.com/t/nHfxoKIaNz
Although in the video clicking the button took a long while (almost a minute), other tests (calling the method normally - not through script extensions) show that both the normal method and the ASync method take the same amount of time - about 13 sec (see below I re-recorded how a successful execution looks like). Therefore I'm unsure that we are even saving time using the ASync method...!
Anyway as you can see in the video (I had to pause it btw, it takes quite a long time to execute fully) after the command to click the button, the button does not apear to be clicked (CMD window is not launched), and TC keeps looking for the CMD window (those are all those delays you can see). Eventually an exception is thrown (not sure why, the code referenced appears OK), the CMD window is finally launched but at this stage TC is no longer responding. You can't see it in the vid but clicking Stop does nothing and ends with the same result as closing the CMD windows (which pop one after the other - not sure why?) - TC crashes. Because it crashes I can't see the logs to understand exactly what is happening.
Anyway I've attached some dumps, maybe you guys can make more sense of them than I.
Obviously this problem is specific to our scripts and our SUT.
Here is a second vid of a successful execution, using normal click method in Script Extensions:
http://screencast.com/t/65z9OZvw6bIB
You can see in the log that it takes 13s between clicking the button and recognising the CMD window - still much too long for such a mundane simple action (this executes allot during a full run).
Any suggestion is welcome!
Thanks
Thanks for the response.
A quick check shows that you are right, the ASynch method works on other buttons.
I have recorded a video to show the difference in execution between clicking the button and using the ASynch method:
http://screencast.com/t/nHfxoKIaNz
Although in the video clicking the button took a long while (almost a minute), other tests (calling the method normally - not through script extensions) show that both the normal method and the ASync method take the same amount of time - about 13 sec (see below I re-recorded how a successful execution looks like). Therefore I'm unsure that we are even saving time using the ASync method...!
Anyway as you can see in the video (I had to pause it btw, it takes quite a long time to execute fully) after the command to click the button, the button does not apear to be clicked (CMD window is not launched), and TC keeps looking for the CMD window (those are all those delays you can see). Eventually an exception is thrown (not sure why, the code referenced appears OK), the CMD window is finally launched but at this stage TC is no longer responding. You can't see it in the vid but clicking Stop does nothing and ends with the same result as closing the CMD windows (which pop one after the other - not sure why?) - TC crashes. Because it crashes I can't see the logs to understand exactly what is happening.
Anyway I've attached some dumps, maybe you guys can make more sense of them than I.
Obviously this problem is specific to our scripts and our SUT.
Here is a second vid of a successful execution, using normal click method in Script Extensions:
http://screencast.com/t/65z9OZvw6bIB
You can see in the log that it takes 13s between clicking the button and recognising the CMD window - still much too long for such a mundane simple action (this executes allot during a full run).
Any suggestion is welcome!
Thanks