I’m trying to do something like this:
TypeText “5”, tab, “3”, tab, “MyFile.txt”, tab, tab, tab, tab, “17”, tab, “No”, tab, “144.3”, tab, “No”, tab, “2009”
Generally, this is a sequence of keystrokes to enter various data in various fields, then process it. The SUT has the tab index set up for fast data entry by the user.
Timing is a problem because often the button “btnProcessData” gets clicked before all the keystrokes have been fully processed by the SUT, resulting in incorrect results.
I can set the RemoteWorkInterval to something slower, and that works okay. I can also put each TypeText on its own line, and that works too, but doesn’t seem as elegant.
Is there a recommendation or “best practice” on how many commands to put on a single TypeText line?
It seems like the RemoteWorkInterval value drives the speed at which the Click gets sent to the SUT following the TypeText line, and not necessarily how fast each keystroke and tab on the long TypeText line gets sent.
This isn’t really a problem, more of a post to discuss how everyone handles long TypeText commands and the (almost guaranteed) timing problems.