Forum Discussion
tuscias
13 years agoNew Contributor
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
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