Hi Dmytro,
Ok so this seems to be a design decision from SmartBear.
I see their point of view but it also means that, when going through the AUT, you cannot see if an object has an Alias or not :-(
I agree with you that you should avoid the extended find if possible. Here is my problem: we would like to run a smoke test on a new build of our AUT without having to spend time on correcting the namemapping. We wish to run the smoketest as part of our Continuous Integration cycle so we need a procedure that is lightweight, dynamic and fast --> having to manually update the namemapping does not seem to fit this :-)
Any suggestions you may have are very welcome as I don't quite know how to overcome this.
P.s. I should mention that we have unique UIDs on all objects. I was thinking about making a script that would search the AUT for these UIDs and then try to link the Alias with this UID but it seems I would be making the namemapping functionality all over again - something I would rather not get into :-)
Thanks for your input!
Regards
Kresten
