Sending any input via keys dramatically slows down testing

[bzh027]

Hello, I've noticed that when testing web login on my application, that either sending [Enter] via keys() or click/clickbutton() dramatically slows down my testing. There is always a 5 second delay, even after reducing the default wait/delay in the project options. Is there a way to force the input any faster? 

I am using 12.0.122

[Marsha_R]

What message do you see in the indicator box when this is happening?

[TanyaYatskovska]

Also, let us know:

- what browser you are using

- if you can reproduce this behavior on a common page, say google.com

Also, make sure that you've installed patches for the latest browser versions:

https://support.smartbear.com/downloads/testcomplete/

[tristaanogre]

Note that you can also, for many objects, use the method "SetText" to send text data to a data entry field. Unless you specifically need to detect keyboard events, I prefer this method.

[bzh027 · Accepted solution]

Wow I restarted the application after the machine had been hibernating for some time and now it is flying. 

To answer the question, it was indeed independent of the application (tested on nytimes.com / browser bar input) and browser(edge/firefox/chrome), but only seemed to affect those three methods (click/clickbutton/keys). setText and all other code executed when expected. The playback description was simply 'playback' when it manifested.

Changes to project options and active extensions were made but it apparently had no effect until restarting the application a couple times. I am not certain of all of the changes I made otherwise I would list them here.

Thanks for the suggestions with setText, I do use that for most keyboard input.

[Marsha_R]

And yet we use Keys for everything with no problem and SetText has been slow and inaccurate for us!  🙂

[cunderw]

SetText is a less valid test as you're performing an operation that a user would not do. Keys uses actual Windows events to perform the operation which is much more realistic.