Forum Discussion

Rakeshyadav09's avatar
Rakeshyadav09
Occasional Contributor
6 years ago
Solved

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?

  • 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.

    https://support.smartbear.com/testcomplete/docs/testing-with/object-identification/name-mapping/how-to/store-images.html

  • cunderw's avatar
    cunderw
    6 years ago

    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. 

2 Replies

  • tristaanogre's avatar
    tristaanogre
    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.

    https://support.smartbear.com/testcomplete/docs/testing-with/object-identification/name-mapping/how-to/store-images.html

    • cunderw's avatar
      cunderw
      Community Hero

      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.