Well...
1) Are you doing script code or keyword tests?
2) Are you using the "Keys" method in your tests?
3) What OS are you using?
4) What component class is it?
5) How is the object mapped?
This is, basically, what we need to know before we can even start to troubleshoot. Generally speaking, the "tab" method works very well for many people so it has to be something unique to your environment/application/implementation.
1) I am creating this specific test using the record and playback so keyword test. Although I will say that I do plan on converting it to a script after it is made working correctly.
2) The operation in the keyword test is Keys yes. I am physically doing the exact same motions I do when it normally works just this time I have the TestComplete recorder open.
3)I am on Windows 7 64 bit.
4) I don't know. What is is a component class/ How do I find that out?
5) It is mapped by its winforms control name.
Out of curiousity... do you have a virus scanner of some sort running on that machine? It's possible that something may be intercepting TestComplete's hooks into the Keys method.
Nope there is no virus scanner on this system.. Like I said before it runs perfectly fine without testcomplete running but when testcomplete is used the tab keys stop working. And even when testcomplete is closed the tab keys still stop working for the application until the application is restarted.. So it sounds like TestComplete is spawning off some other process capturing the tab keys or something.
That is truly strange... Again, I can't imagine what it could be.
At this point, your best bet would be to contact SmartBear support directly. They may have some hints as to what to try.
Hi,
> 2) The operation in the keyword test is Keys yes.
Just a wild guess: if the parent of the .Keys() method is something else but the control you need to press a Tab key for, change the operation/code so it used this control and check if it helps.
Some pseudocode to illustrate:
var form;
var control1 = form.control1;
var control2 = form.control2;
control1.Click();
form.Keys('[Tab]'); // <== if test contains something like that change it to control1.Keys('[Tab]');
...
