ContributionsMost RecentMost LikesSolutionsRe: Best Practices You mentioned that you have stopped using name mapping. I also read somewhere that some users only map windows or dialow windows and not all the needed UI elements. Can you help me understand how this is done? Or can you point me to the forum that discusses how this is done? Aside from using name mapping, how do you handle a desktop app which has hundreds of similar fields? I'm automating a WPF application which has hundreds of fields in one screen. Now most of them are of the same type and only differ in the WPFControlName. Adding all these fields one by one and editing them in the name mapping, does not seem very efficient. I know that you make use of find method to dynamically create objects. I'm thinking of creating a loop that would go through perhaps an array containing the different WPFControlNames and create an object for each. But I'm fairly new to TestComplete and scripting, and I'm not sure where I should be placing this code. Do I put it in a separate unit? I don't want to have to use the find method everytime I need to use the field/object? Re: Does TestComplete has a feature that keeps track of called and calling functions/keyword tests? Thank you Robert. Your articles really helped me get started with TestComplete and gain a better understanding of test automation. Do you have recommendations on how to keep track of all these functions or at least ensure that when you make changes to one function (e.g. changes in name and parameters), all the other functions/keyword tests that are dependent to it would be updated? Or is this a valid concern? Did you run into this sort of trouble before? Does TestComplete has a feature that keeps track of called and calling functions/keyword tests? I just noticed that when you change the name or parameters of a called function/keyword tests, the calling functions/keyword tests do not automatically get updated. And so running these calling functions/keyword tests would result to an error. Does TestComplete has a feature that does this (automatic update)? If so how do I enable it? Or is there a way for me to keep track of the calling functions/keyword tests (aside from doing it manually through documentation)? SolvedRe: Object Spy is no longer able to identify a UI element which was being properly identified before. Build was the same. But I did try recompiling and it's working fine again. Odd. I'll continue working with this and see if I encounter this issue again. Thanks sanjay. Object Spy is no longer able to identify a UI element which was being properly identified before. I'm working with a Silverlight web app. We've already made the necessary preparations needed to support Silverlight controls. Just yesterday, I had no problem highlighting or identifying Silverlight UI elements using Object Spy. I was already able to map them and I've already created and ran several tests. After I restarted my machine, all that Object Spy can identify are the main windows/panels. It is no longer able to identify child buttons, dropdowns, checkboxes, scroll bars, etc. The tests are now failing because they are no longer able find the mapped objects. How can I solve this? I don't remember making any changes to the settings/project properties. Solved