Unintended actions during keyword test run

Hello ashly 

I understand from your description that your single click action is performing two independent click actions, and that is for sure interesting and illogical.

To help you isolate and probably make sense of it:

1. Reboot
2. In a new test project, record only the single click action
3. How many KeywordTests Item and what Operation? I would assume a single Click Item
4. Select that Item and right click, and from the speed menu select and run a) "Highlight on Screen" and b) "Run Selected Operation"
5. From the log, view the picture to see where TestComplete clicked

• Did TestComplete recording include only a single Click Item or two Click Items?
• Did "Highlight on Screen" and "Run Selected Operation" execute as expected?
• What do the log statement and picture tell you?

This is an interesting problem for sure.  You may indeed be able to sort it out by looking at the object properties or the specifics of the line in the Keyword test that is executing the click.

However, another avenue is to take a different approach.  Often in TestComplete the same thing can be accomplished by more than one method.  In this case I would suggest trying the Keys method to accomplish selecting the tab you want.

The first step is to see if your application supports keyboard access to the tab.  With focus on you application press your Alt key.  If the application supports keyboard accelerators for the tabs you should see them displayed something like below.

Here you can see "H" selects the Home tab, "I" selects Insert and "T" selects Tools.

If you see them then this approach will likely work.  In your keyword test you'll want to select the "Call Object Method" entry in the Test Actions list.  Then select the main application window as the object.  From the list of methods choose "Keys"

For the value enter "~" followed by whatever keys(s) your application showed for that tab.

Click "Finish" and run it.  Hopefully it works.  

But I have also tried the same without namemapping and there also it failed. No mouse coordinates are used.

You need to verify your name mapping and property values correspond to the UI object you are referring too. Verify that you are not using mouse coordinates, and ensure each of your actions are correctly defined.