After doing some research on Name mapping, I think this requires high maintenance, as things change you keep updating the Name Mapping. Is that right?. I think it is better to write the scipt and find the object that we want using NativeWebObject method then perform actions.
Please let me know if I am doing the right conclusion.
For our Web application, this has become invaluable because, as DIV's and other such change on the application and hierarchies and the like change, name mapping allows us to be able to use a consistent alias for every component. Additionally, there's a feature called "Extended Find" that allows you to map an object but then, if it moves into a deeper child object or similar thing, the name mapping engine can still find it.
[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
I'd like to note that the Name Mapping feature allows:
- changing objects recognition criteria without changing your tests;
- changing the recognition criteria dynamically from your script;
- finding an object regardless of its position in the hierarchy;
- updating your Name Mapping scheme dynamically during the test run.
Did my reply answer your question? Give Kudos or Accept it as a Solution to help others. ⬇️⬇️⬇️