Ask a Question

Test Complete Looses Aliases

Occasional Contributor

Test Complete Looses Aliases


I have built alot of tests with Test Complete, however suddenly my aliases have changed inside of the system. For instance:




Became:"JPanel", "", 0).SwingObject("JToggleButton", "Log Viewer", 3)


Im not exactly sure how to proceed all of my tests are now broken and ill need to refactor them to allow for these new paths. Any suggestions?

Valued Contributor


Not sure to understand but your first line is a mapped object but your second is not a mapped object, you have for example instance numbers...

assuming all that has changed is the name of the process ("javaw" became "java"), you should open your namemapping and just rename this single thing in the mapping tree.

Occasional Contributor

What im saying is the path changed quite a bit using the object spy i get this"JPanel", "", 0).SwingObject("JToggleButton", "Current Status", 1)

What i got last time is

Are you relying on the automatic mapping (it looks like it)? If so that will never be reliable. You will have to manually manipulate the attribute used to identify you objects to something that is not dynamic.


What it looks like is the panel JPanel for your ToggleButton was mapped with an identifier that is dynamically generated. You also have a full list of aliases that aren't really doing anything for you since you will never interact with things like RootPane, contentPane, etc...


If you have't I suggest reading trough the documentation here: as well as watching some of the training videos SmartBear provides. Namemapping takes practice and trial and error to get a solid and reliable mapping setup.


Click the Accept as Solution button if my answer has helped
Community Hero

I understand that in your current situation you can't run the test.

Back up your project and run TestComplete with an option where TestComplete itself dynamically updates NameMApping data in the repository and see what the results will be.


This option is in:


Tools -> options -> Engines -> NameMapping

SmartBear Alumni (Retired)

Thank you everyone for participation in the discussion. 


Hi @mmccollum, did you manage to solve the issue? What approach did you use? 

Sonya Mihaljova
Community and Education Specialist

Occasional Contributor

Honestly no I havent yet, I went around the problem by using a namemapping file from another instance of test complete that was working and that seems to fixed it for now, however it may not work forever.

SmartBear Alumni (Retired)

@mmccollum , I see.

Glad that you managed to make it work using this workaround. I’ll mark this as a solution for now.  

Sonya Mihaljova
Community and Education Specialist

Showing results for 
Search instead for 
Did you mean: