Solved
Namemapping nightmare
Hi, I am new to Testcomplete and having trouble with namemapping. I am using Testcomplete to test a WPF based application. The issue is that UI on the application keeps changing, and each time ...
Forum Discussion
Greetings
I've recently encountered an issue with all of my namemapping becoming broken after some recent updates. It is doable to remap everything, (but it is a LOT!) - I stumbled upon this post and it sparked some ideas I have had in the past of using FindAll/FindChild to return a list of what elements are available. Then I can write functions to test those elements after I do a scan of the page.
After reading the suggestions above it seems that this is logical, but definately need a starting point.
Some of the elements I have name mapped are extremely long and this is going to require some thought.
An example is:
Aliases.browser.page.panelRoot.Section("TEST").Panel(0).Panel(0).Section(0).Panel(1).Panel(0).Panel(0).Panel(0).Panel("form_item_").Panel(0).Panel(0).Panel(0).Panel("form_item_test_name").FullName
Any advice is appreciated! Thanks
Hi,
First of all....
.... what you showed is your Alias, not your mapping. There's a difference. The Alias has no need to be that long. you can collapse a LOT of those "panel" objects down in the Alias while preserving it in your mapping. That way, when you need to what you've currently described, you can move objects around in your mapping and preserve the Alias.
Second of all - FindAll/FindChild are good for occasional searches... but they are searches. NameMapping processing has a lot of optimization built into it so the recommended way is to map everything you can and use FindNNNN methods for those things that are variable enough (like tables of data that have variable length, etc) that make it cumbersome to map accurately.
One approach is to build and use Your own framework to access Your app's objects.
I only use name mapping and aliases for basic addressing - of the dialogs, but not for the hundreds and hundreds of fields thereon.
So, in Your framework, provide a dialog object and make use of an alias to access it. For the child controls, use Your own Control objects and for their addressing Your own addressing methods.
If data or functions are scattered to some technical ui objects, You can hide this inside Your control object.
This is some work to do, but it gives You a stable and maintainable result.
Thanks for your reply and that does sound like a good approach.. Can you by chance elaborte a bit, as I understand the concept but would like to understand specifically how to achieve an example of this in TC. Thanks again.
