Forum Discussion
makh_dv
13 years agoOccasional Contributor
Kresten,
Now I see what you mean. :-)
It looks this is feature according to following answer:
Old SQAForums thread by Allen_AQA :
"In this case,
the behavior is expected as getting mapped names for objects retrieved
via the Extended Find feature can lower your test's performance
significantly due to complex tree processing. So, the MappedName
property is not available to objects that can be found using the
Extended Find feature, and the behavior is unlikely to change in the
future."
From my own, I would NOT suggest to use Extended Find widely. Only if object is really "jumping" on hierarchy in one run, not from build to build.
Being on you place I'd try to use Aliases structure for your tests and try to keep NameMapping organized.
Especially imagining what Extended Find means internally and what impact it can have on performance for object recognition during run.
Now I see what you mean. :-)
It looks this is feature according to following answer:
Old SQAForums thread by Allen_AQA :
"In this case,
the behavior is expected as getting mapped names for objects retrieved
via the Extended Find feature can lower your test's performance
significantly due to complex tree processing. So, the MappedName
property is not available to objects that can be found using the
Extended Find feature, and the behavior is unlikely to change in the
future."
From my own, I would NOT suggest to use Extended Find widely. Only if object is really "jumping" on hierarchy in one run, not from build to build.
Being on you place I'd try to use Aliases structure for your tests and try to keep NameMapping organized.
Especially imagining what Extended Find means internally and what impact it can have on performance for object recognition during run.
Related Content
- 7 years ago
- 5 years ago
- 11 years ago
- 8 years ago
- 7 years ago
Recent Discussions
- 13 hours ago