Hi!
Yesterday I created a new test. and I have a few problems with the name of the buttons
the original name is
Aliases.FelixHaupt2.GastBeziehungenDlg.bsSkinPanelClient.bsSkinPanel2.bsSkinPanel3.VCLObject("bsSkinButtonClose")
In Teststep it is recorded with ''Label21'' which can't be found, (doesn't exist)
Any idea?
See photos below
Since i got the debugging infos, TC found the correct button.
Thanks to all
By the way, is it possible, that it not works correct, because of "missing debug info".
by the way, i found out, what label 17 is.
Its a label which was on the window behind the window, i worked with.
wondering why this could happen. clicking on a form, and test complete takes something from the hidden form
Hi tristaanogre !
Yes its strange.
Was there an overlapped window? No. My button was on top.
But in this moment i clicked the button, Test complete took the window under my GastDlg object.
I sometimes realized this phenomen in my Project before (I wanted to create Checkpoints, and TC was'nt able to find the correct *peep* and took the window behind).
Maybe that 'missing debug info' is the problem. I got a new Version where debug infos are included now. Hope it helps.
Maybe it's a problem with delphi? Delphi 10 i think.
Recording my test, and after this reorganizing it. Yes thats the thing I do. First of all i should test it, like a 'DAU' (means a user which doesn't know anyting in austria - don't know the english word for it)
But my boss told me to ask in the Forum, what the problem could be, if someone has the same problems with Delphi.
By the way. Making Checkpoints, Do you do this during recording or afterwards when you correct the test.
Petra
Hi Petra,
I test delphi apps, so I want to says some stuff about this :
Having a label named originaly "label23" for example means that the developper didn't done its work completly. And, if you map the object now, and if he (or she) corrects the label naming your script will not work anymore. You will have to remap it further.
I never use debug infos. In delphi, there is compilation directives that allows you to incorporate debug infos in the executable file, but you have to test the executable in customer's background. having debug info will give you another background.
But, you could ask the developper to put all the debug infos in a separate file which needs to stand aside the executable file.
said differently, I hardly recommend to deal with the lack of debug info.
there are almost always a way to do so.
With a lot of the grid and tree controls I have to deal with, they would be impossible to work with without the debug properties and methods.
