Finding Objects Delphi
Hi there. Sometimes Test complete can't find the right object. The correct name of the object (marked in red in attachment) is DBText12. Every x-th time TC says "No the name isn't DBText ...
Forum Discussion
The crazy one is this
I have several test-steps.
This "opening the Table" about 15 or 20 times in the whole test.
the first 10 times it works fine, in the 11 test it crashes. or 1 works, the next crashes.
My Test is splitted in several "mini-Tests" (dont know the correct word)
1 i open my .exe file
2 logging in
3 opening the table
4 adding coca cola, beer and so on on my table ( like a waiter will do)
then different actions.
repeating the 4 teststeps above.
next action
....
So i dont think the problem is the namemapping.
Without knowing EXACTLY what the other steps you do are.
Or EXACTLY how the application is responding to these steps.
You're not likely to get an exact answer. Just potential pitfalls.
You say you repeatedly re-use the same controls. But we don't know what you do within each of these repeats. Or how the application state is changing as a result of your tests. Presume other things are also happening, not just constantly clicking on this same field/button? Much as I'd love to assume that everything stays the same, I can't. And neither should you!
It's kind of hard to say what's happening. But you posted the error yourself. Object not found. To which I've already mentioned two possible things that could be causing that.
But if it's happening intermittently (you say sometimes the first time you use it, sometimes the 11th) then it sounds more like a sync issue - ie. Something is usually ready at the point you try and use it, but not always. So you may need to verify that objects are in a ready state (an action on a previous object will often affect the state of other objects) before you attempt to use them.
A photo of the object spy will not necessarily provide the answer if it's a sync problem.
By the time you screenshot it, yes .... the application has caught up and the object has rendered and enabled itself fully. So everything looks fine. But at the point your test tried to use it, that may not be the case. That's what a sync issue is.
Colin_McCrae wrote:
But if it's happening intermittently (you say sometimes the first time you use it, sometimes the 11th) then it sounds more like a sync issue - ie. Something is usually ready at the point you try and use it, but not always. So you may need to verify that objects are in a ready state (an action on a previous object will often affect the state of other objects) before you attempt to use them.
I'm with Colin_McCrae... scripts tend to run faster than a user usually does them... and they are pretty "stupid". They will attempt to do something without first making sure that you CAN do that something. As a human user, when you're going through your application, there are hints that you need to wait before you can proceed... like mouse cursor shape, messages, on screen, etc. So, you need to make your automation "smart" to do this kind of stuff.
The simplest way around your problem, if it is a sync issue, is to do some sort of check of the existance or readiness of the object in question before you attempt to interact with it. "Object not found" is easily resolved by either increasing your global Auto-wait timeout (the installed default is 10 seconds) or by utilizing the WaitAliasChild (or WaitChild or WaitNNN method) to wait for the child object to return before proceeding and then checking the "Exists" property on whatever is returned to make sure that, yes, we got it.Seems like it is a timeproblem
Standart autowait timeout is set at 1 minutes . :catlol:
Maybe i will make a delay.
Checkpoints: In case of failor its not possible do reach any button or text.
By the way. i tested my program in midday, I dind't change anything, and it worked.
Thanks to you two
petra wrote:
Seems like it is a timeproblem
Standart autowait timeout is set at 1 minutes . :catlol:
Maybe i will make a delay.
Checkpoints: In case of failor its not possible do reach any button or text.
By the way. i tested my program in midday, I dind't change anything, and it worked.
Thanks to you two
OK, first of all... AVOID hardcoded delays if at all possible... aqUtils.Delay is nice... but if the circumstances chance, you'll end up having to change code... again... that's why you should use WaitNNN methods and set the wait time sufficiently high to cover all contingencies... it avoids hardcoded delays and yet still allows your tests to work around synchronization issues.
As for your last statement, DEFINITELY a performance issue in your environment. Something slowed down your machine early on so that, now, it's working better. I'd suggest investigating that line of things as well that, if you know you're going to be running your tests during a particular time frame, make sure that nothing is going to impact performance.
