Hi Sonya,
We are not passing any aliased or namemapped object from keyword test as did not find solution for that.
But will try to minimize usage of xpath as per advice given.
Hi Alex,
Thanks for your reply. We are looking to get the ContentText of the objects (Not mentioned in the function code snippet). At the moment, we are passing Xpath of the objects and internally getting the content text of these objects after which converting to a string format with delimiter ";" as per the functionality check required for our application.
Any other workarounds possible excluding name mapping as you've mentioned the pitfalls that could arise?
The client wants us to only use name mapping for all check but we think xpath is an easier alternative :-)
Hi,
> The client wants us to only use name mapping for all check but we think xpath is an easier alternative :-)
Generally speaking, I am with your client.
While it may depend on the given tested application, Aliasing is usually a much better approach when compared to XPath.
Something that might affect your code:
-- If XPath finds the sought for object, then either TestComplete's wrapping object or native DOM object may be returned. Native DOM object does not have .Exists property (and others, provided by TestComplete). So you will have to either figure out what object was returned as a result of the search, or use only native DOM properties in your test code.
-- If XPath does not find the sought for object, then null is returned. Which means that you cannot use object.Exists approach that is native for TestComplete.
> We are looking to get the ContentText of the objects
Again, if the native DOM object is returned as a result of XPath search, then this object will not have .ContentText property as it is provided by TestComplete:
