Forum Discussion

petra's avatar
petra
Contributor
9 years ago

incorrect naming by making the teststep

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.bsSkinPa...
  • petra's avatar
    petra
    9 years ago

    Since i got the debugging infos, TC found the correct button. 

    Thanks to all

tristaanogre's avatar
tristaanogre
Esteemed Contributor
That is strange. A mouse click on a component, as you are doing, should send the click to that component directly.

Is it possible that the other window popped up during the test and was, temporarily, overlayed on top of the button you want to click?

Looking at the screenshots, what is aliased as "Gastdlg"? That's what's actually getting the click, not the button you want to.

Try manually editing your keyword test you have recorded and replace the GastDlg object with the button you want clicked and see if that corrects it.

Generally speaking, recording a test is good for getting a general idea of how things are supposed to work. But ultimately, you're going to want to do manual construction of your tests to correct small descrpencies like this.

Hope this helps!
petra's avatar
petra
Contributor
9 years ago

Hi 

 

 

 

 

 

 

 

  • Colin_McCrae's avatar
    Colin_McCrae
    Community Hero
    9 years ago

    If it's a Delphi application, you definitely want a properly compiled debug version. Without this, you will be missing a lot of native methods and properties and things will be MUCh harder to work with.

     

    Not sure whats going with your button.

     

    I do notice in the last screenshot that it has a child item? This may be the label? 'Label 21', 'Label 17' etc is not helpful naming. No idea what they relate to. They may also be using some clever tricks to show and hide objects on the screen. I've run into that in a Delphi application before. Although, in your first post you call it 'Label 21'. In your second one you call it 'Label 17'? Is this the same object? Something is not right somewhere ....

    • petra's avatar
      petra
      Contributor
      9 years ago

      Label 21, Label 17 are 2 different labels.

      Colin you see the window 'Gästestamm'' in background of my window with the selected Button. (picture2 in my first post)

      In this 'Gästestamm' there are different Labels. eg 'Vorname' 'Nachname' 'phonenumber' and so on. 

      Maybe the programmer didn't have enough of time, to rename this while programming :-) so they are callt Label XX

      While i clicked my Button, Test Complete seemed to klick through the button and took the 'Gästestamm' and found Labels instead of a button

      Sorry for my English :-)

       

      New Compiled Version is much better now.

      • Colin_McCrae's avatar
        Colin_McCrae
        Community Hero
        9 years ago

        OK.

         

        So - Gästestamm - is the pop out window.

         

        How did you get - Aliases.FelixHaupt2.GastBeziehungenDlg.bsSkinPanel​Client.bsSkinPanel2.bsSkinPanel3.VCLObject("bsSkin​ButtonClose")

         

        Did you map the object originally?

         

        It appears to be a "Business Skin" button. I've never seen these so I'm not sure how they behave.

         

        And I mention "Label 21" and "Label 17" as in your first post, you say it found "Label 21", but in your third one, you say it was "Label 17"? Your screenshot shows "Label 21", so I'm not sure where "Label 17" is coming from?

         

        Can you inspect the button manually with the object spy? Does it show correctly in that? If it's only a problem during playback, it may simply be a timing issue ....

  • tristaanogre's avatar
    tristaanogre
    Esteemed Contributor
    9 years ago
    Well, to be honest, I rarely use recordings of actions as the actual tests themselves. When I do a recording, it's usually just to get an idea of the order in which things are done and then I manually construct the test. So, in your case, I would edit the recording and replace the "bad" component with the correct one and see if that corrects it.

    As for your question on checkpoints, as noted, I manually create tests usually so the checkpoints I add are a mixed bag. Sometimes I put them in as I'm going, sometimes I go back and add additional ones that I think might be useful.

    As for it being a problem with Delphi... it's been several years since I've worked with a Delphi application but I do recall that there are some strange behaviors like you've described. Usually, they have to do with speed... that you are recording the test but, as you record it, the test recorder in the background is not keeping up with the application under test. So, while the ACTUAL action clicked on the correct window, TestComplete's recorder tool may not have recognized the new window yet. Try recording at a slower speed, letting each window and form fully load up before clicking the next button.

    In the meantime, your short solution should be to manually edit your recording and correct the "bad" component and replace it with the correct on.
    • petra's avatar
      petra
      Contributor
      9 years ago

      Since i got the debugging infos, TC found the correct button. 

      Thanks to all