Unable to see Dropdowns
We had a suite of tests which worked fine! After the latest patch from our third party devs, the tests no longer run. The main issue relates to dropdowns; formerly, a user could hover over a menu...
Forum Discussion
If it's a dropdown control, you SHOULD be able to skip the "DropDown" call and simply go to the "ClickItem()" call. Would be helpful to see an object spy of the control in question, just to be sure.
Excellent! The ClickItem call worked perfectly - that's a big relief - thanks tristaanogre, Colin_McCrae baxatob
Really?
You're right though. I just tried it myself. An unknown method causes an "object cannot be found" error. I didn't realise that. I'm sure I'd seen "Method Not Supported" errors for this sort of stuff in the past? Maybe that was in VBScript? I'm using C# Script at the moment.
I guess it doesn't help when the log entry contains a "More info on this error" link which takes you here:
Ah well. You learn something every day .... :smileyhappy:
No, if the method is not supported, the error should be: Unable to find the object DropDown. The object with the specified attributes does not exists.
I have specially checked out at my side.
Something I've seen show up lately is that sometimes calls to methods (linkForm.DropDown()) actually ends up as an object Not found, not on the parent item but it seems to be trying to identify "DropDown" as an object, not a method... especially the case when using JavaScript/JScript... So... you could BOTH be right :catvery-happy:
Nice to hear... But still interesting, why DropDown() was selected by default :)
lol
OK. It wasn't an object not found problem then. It was an invalid method .....
Colin_McCrae wrote:
lol
OK. It wasn't an object not found problem then. It was an invalid method .....
Obviously yes. But as I understood it was selected automatically by TestComplete during recording.
Oh yeah. Agree on that.
But the error, when asked about, was "object not found" on the dropdown component.
But it obviously was being found. And the method (which I presume was valid on the old TextNode) was no longer valid once it changed to a Link. So I doubt the error generated was actually "object not found", but more like "object does not support this method" or something like that.
The "not found" part was a red herring in other words .....
