Backticks in textboxes using the Keys command
Related to ticket from 2 years ago: testcomplete-questions/testexecute-enters-in-textbox/247032 Somehow, during the test run when using Keys, sometimes a ` (backtick) is entered into the field. O...
Forum Discussion
Out of curiosity, how are you interacting with the field?
Do you just send keys to the field, or tab / click so the cursor is in the field before you send keys?
I click on the field to make sure my cursor is in the field before I send my keys, I don't have the large amount you have but never had problem with it.
Just the keys method in most cases, After searching TC does over 3500 keys entries, so adding a click/focus before every one just isn't possible.
Before considering any course of action and for the sake of isolating such anomaly root cause, perhaps you could create an isolated test project to experiment with by looping to reproduce the problem. Once consistently accomplished, and in the same loop you can experiment with possible work arounds such as click in the field or lead the key strokes with Ctrl+A.
Such suggestions are not the solutions, just ideas to help you move a step forward. Worst case scenario would be to apply work around to handful of fields that exhibit such odd behavior, and I think that would be a good idea.
I made a checking loop last Friday that tests the fields from the examples. It presses [Enter] 10,000 times in one field and 1000055[Enter] in the other field. Unfortunately, this issue did not arise.
It took about 2.5 hours for both fields, and there were no issues.
Trying to force this issue is a hard problem, it doesn't happen often enough for me to determine why it occurs.
I checked the Windows Event Viewer, searched most if not all of the internet, and I can't seem to find anyone else with this issue.
EDIT: it ran for 3 days btw, I dont want to leave that on since it messes with my normal tests.
In that case it is logical to conclude that it is not TestComplete keys operation, nor the application. Sequence of events and combination of involved technology stack could hold the cause, and that is impractical to pursue.
I would give up on explaining/fixing it and add to my routine a check to ignore, log warning, and move on. I had to do that for Salesforce application, only after a long run a test case would bring up a specific page with fields incorrectly as read only.
