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,
I am not sure that I've got the whole idea...
You must use code in order to create an array of objects. Then you should be able to pass this array to keyword test as a parameter. (Never tried this, thus this should be checked.)
While you can create an array of NameMapped (better - Aliased) objects and pass it to some other function, this is usually not the best idea in TestComplete's world. The case is that Aliases object in TestComplete caches actual objects and tries to reuse them. The problem is that if aliased object is recreated in the tested application (e.g. table with data has beed recreated as a result of some ajax request and page script), its cached copy becomes invalid but is not destroyed and can be refreshed from test code. So, the longer test code passes Aliased object through function calls, the higher the chances (especially, for web applications) that the object will become invalid. In order to prevent false negative failures, test code should always consider whether or not the given object must or may not be valid and proceed appropriately.
Obvoiusly, for performance considerations your test code should search for tested objects as little as possible and use references to the found ones as long as possible. But on the other hand you must consider the life time of this or that tested object in the tested application and search for the new or recreated object when needed.
> reportNameArray.push(nameMappingArrayOfObjects[i])
> var reportName = reportNameArray.join("; ");
While technically it might be possible to join an array of complex tested objects into a string... What output are you expecting for?
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:
