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
Hi petra,
if it's a timeout issue and you're waiting for an object to appear, you'll need to implement this function (that is in SmartBear's sample files)
function WaitAliasChildFunction(object: AliasObj; Name: string, time: integer):Boolean;
var AliasObj;
begin
// Specifies the Alias object
AliasObj := object;
// Checks whether the Font window has appeared within 10 seconds
if (AliasObj.WaitAliasChild(Name, time).Exists) then
begin
Result:= true;
Log.Message('Element found : ' + Name)
end else
begin
Result:= False;
Log.Message('Elément not found : ' + Name);
end;
end;
----------------------
if you want to use this short script you write :
if (WaitAliasChildFunction(Aliases.Kasse.ArtBei, 'DBText12', 15000)) then
... etc
----------------------
in this script, you could put everything as a child. and you won't need to wait for 15 seconds (in this example) : when the DB will be in memory, the counter will stop and it will do the "then" block
That will not work 100% of the time.
It depends how your developers are removing or hiding objects.
My application is Delphi. Some objects, when they are not in use, are hidden. Some are destroyed. So I can't rely solely on exists. It's not enough. I have to check Exists, VisibleOnScreen, and for one particular control (I can't remember what type off the top of my head) I have to check a Field value as well as VisibleOnScreen is not accurate for it either.
I'm part of the dev team, and we don't specialy hide objects. but... this script is an example. In my toolbox, in TestComplete, I implemented several scripts that wait for particular properties. but the logic is the same.
enabled
enabled and visible
not visible
exists
not exists
etc etc...
you could wait several properties one after the other by doing loop into loop.
but again, as a dev I don't hide controls. I just act on some of its properties, and I have the source code to know what I am testing.
Yep.
Just pointing out that the example snippet won't guarantee you 100% accurate results. In case the person asking the question didn't realise that.
You're very much at the mercy of the development team with stuff like this. Especially as most Delphi applications these days tend to be fairly mature. So various different devs will have worked on them. Each with slightly different ideas about how things should be done. So you end up with 6 different ways of achieving the same thing! That's certainly been my experience with a mature Delphi application .....
In case of that the teststep mostly works and sometime fails, i dont think that our dev removed or hided the object before/after using it. But i will ask him.
Thanks, i will put this piece of code into my test and look, what will happen
.
