Ask a Question

Committing a Name Mapping file

Occasional Contributor

Committing a Name Mapping file

Whenever I add objects in the project's Name Mapping file and I try to commit the file, then it shows me to commit the images (png file), images.NMing and tcCfgExtender files along with the Name Mapping file. Is it compulsory to commit these as well with the original Name Mapping file?

If I'll ignore these files, does this impact the Test execution?

Esteemed Contributor

The extender file is actually one that should be excluded as it is a configuration file that is machine specific.  You should make sure you have that in your .ignore.

As for the image files, they should not prevent execution if you ignore them.  It's a feature of TestComplete that, when you map an object, it stores an image of the mapped object for reference.  You can configure TC to NOT store those images.

Robert Martin
[Hall of Fame]
Please consider giving a Kudo if I write good stuff

Why automate?  I do automated testing because there's only so much a human being can do and remain healthy.  Sleep is a requirement.  So, while people sleep, automation that I create does what I've described above in order to make sure that nothing gets past the final defense of the testing group.
I love good food, good books, good friends, and good fun.

Mysterious Gremlin Master
Vegas Thrill Rider
Extensions available

Personal experience. The images don't do much as far as test reporting, especially when you're doing more data driven and dynamic testing. They take up a lot of space in source control. 


If you need them though, there would be harm in keeping the image in source control. 


Click the Accept as Solution button if my answer has helped
Showing results for 
Search instead for 
Did you mean: