Possibility to split the NameMapping into different files per project

Hello,





Unfortunately, currently, TestComplete does not support multiple name mapping items in the same project. We have a request for this feature, and your post has increased its rating. Thank you.

Is there any progress in implementing this feature? This is highly wanted here.



Best regards.

Still the same problem in the new version.

Hi,



Please implement this feature and let me tell why it would be useful.

It is normal that new AUT releases introduces new features (sometimes implemented using different technologies).

This means that some portions of name mappings becomes outdated and useless. As we started versioning automated tests it became difficult for us to manage all the new and old release mapped objects. With scripts is it ok, but namemapping is the same for all releases. Currently we a test repository which takes about two weeks to run all the tests (I mean running tests 24/7). And we have four versions of this repository and of course this numbers will increase in the future as we have to support older releases.



Merging NameMapping changes between test automation team workers is a pain in the a**. All these xml node index rotations, insertions etc. it reduces the joy of using your software greatly. We have over 20 test applications and utilities and all of them are changing at a different pace. Currently our name mapping file is 6MB in size. We have one namemapping file for all our test applications because you can have only one in the project and during test sometimes you need to use 7 of them so having multiple namemapping for different projectsuites is not an option.

As we have a shared script library which is the same for all test repositories we would like to have the same pluggable functionality for name mapping. This way we could have namemapping for each test application and join only those parts needed for the test.



Conditional namemapping is excellent feature, but please don't stop there.

Thanks

We are now at a point where we are working with 3 testers on the same NameMapping.tcNM file. This file is getting quite big (currently about 4 MB) and merging does not work without manual intervention afterwards. Our wish would be the possibility to have several NameMapping.tcNM files per project. For example, currently, we have the name mapping for components of Adobe Reader in the same file as for our application. We would like to have one AdobeReaderNameMapping.tcNM file and one OurApplicationNameMapping.tcNM file. This way we could rework the Adobe Reader file once there is a new version of Adobe Reader minimize the size of OurApplicationNameMapping.tcNM As a further step we even would like to differentiate between parts of our application, e.g. OurApplicationLoadingNameMapping.tcNM OurApplicationSavingNameMapping.tcNM If you support this wish as a user please reply to this thread and let the support see, that this is a worthy feature. Happy developing.

Totally agree with this request.

Namemapping should be built more flexible and maintenance on the Namemapping should be more easily. Splitting the Namemapping into parts would be a good start.

This would be so helpful. We are constantly overwriting each others name mapping and haven't found a way around it except to not work on it at the same time. Please make this a priority.



When my coworker saves, if I say yes to reloading I lose my changes. If I say no, when I save, she loses her changes.