Forum Discussion
Hi Ulrich,
Some example will help... but my current guess is that you are talking about .QuerySelector() and .QuerySelectorAll() methods provided by TestComplete.
I did not use them (and this seems to be not mentioned in the documentation), but I think that they behave exactly like the .EvaluateXPath() and .FindChildByXPath() methods. I.e.: if the found web element can be matched to the object from the Object Browser, then the matched object is returned. Otherwise, native DOM element is returned.
If the above is correct, then the objects that you are talking about should be either native objects/interfaces provided by the given web elements (and thus you should read relevant DOM documentation) or are provided by Python itself (and thus should be addressed in Python's docs). Though I really doubt about latter and tend to think that this is something from the native DOM area...
Hi Alex,
right, wie use the QuerySelector methods provided by TC. They work fine. And they give back these wrapper objects where up to now I did not find a pythonis way to look into them - just becaus they are a kind of com objects coming form the language TC was written in.
So as far as I see I have to try with the DOM object definition and then coding a try and arroe method to identify the DOM object behind the wrapper. Not very elegant but I think it is the only way. What I was dreaming of was a kind of dict-method as known from python to get a api information, but ...
Regards
Ulrich
- AlexKaras7 years agoCommunity Hero
Hi Ulrich,
I am not sure that I got what exact problem do you have and why you cannot use TestComplete objects in your test code. Can you provide some specific case so that we can look for specific solution and consider if it can be made generic?