Forum Discussion

Ryu's avatar
Ryu
Contributor
7 years ago

TestComplete sees same window with different properties on different runs

Sometimes, when running a test on an application, TestComplete sees the main window as ClassName: TMainView / ObjectIdentifier: MainView (how it was originally mapped).  Other times, TC sees the same...
  • tristaanogre's avatar
    tristaanogre
    7 years ago

    OK... Now I understand.

    You have the same object mapped twice (In your project, you go to NameMapping and those two items are there).

    Basically this: Delete one of those mappings.  The Mapping is how TestComplete identifies an object.  So, it appears that, somehow, the same object has been mapped twice.

     

    My guess is that the second one (The one maped as WndClass: TMainView) is going to be the most accurate.  I'd delete the first one and see if that corrects your issue.

  • Ryu's avatar
    Ryu
    7 years ago

    I actually don't have the second one mapped; I mapped it a few times when the first one broke just to see what was happening, but then I deleted it.  Next time it happens I will try remapping everything to the second one and delete the first and see what happens.

Ryu's avatar
Ryu
Contributor

tristaanogre, I'm not entirely sure what you are asking, but it is either mapping it as ClassName TMainView or WndClass TMainView.  It's a toss up between which one it decides to see.  I have it mapped as ClassName TMainView and it does see that most of the time, but every once in a while the test fails because it can't find the window (that is when it sees it as WndClass TMainView, but I don't keep that mapping around).  In that case, restarting the test will make it see the correct mapping.  But I would like to not have to restart the test in the first place.

tristaanogre's avatar
tristaanogre
Esteemed Contributor
7 years ago

If the WndClass property is available on the component ALWAYS as TMainView (regardless of mapping), edit your mapping to use that instead.

 

I'm not sure why it keeps changing... not enough details.  However, you can make a change to your mapping to use something that consistently works.

  • Ryu's avatar
    Ryu
    Contributor
    7 years ago

    tristaanogre, I apologize, but I'm still not sure what you are saying.  Can you clarify a bit more?  I will also try to be more clear with what I am experiencing.

     

    I am using application ProcessName (Alias) and it has a MainView window.  NameMapping will either map the MainView window as one of the following two mappings and associated properties:

     

    1. ProcessName.MainView
      1. ClassName: TMainView
      2. ObjectIdentifier
    2. ProcessName.wndMainView
      1. WndClass: TMainView

     

    Any given run will see one or the other mapping; and if it doesn't see the one that I am telling it to use (the first one in the above list), it fails.  I am not changing the test, nor am I changing the application.  I can literally run it and it will see one namemapping, and then click run again and it sees the other namemapping.

    • tristaanogre's avatar
      tristaanogre
      Esteemed Contributor
      7 years ago

      OK... Now I understand.

      You have the same object mapped twice (In your project, you go to NameMapping and those two items are there).

      Basically this: Delete one of those mappings.  The Mapping is how TestComplete identifies an object.  So, it appears that, somehow, the same object has been mapped twice.

       

      My guess is that the second one (The one maped as WndClass: TMainView) is going to be the most accurate.  I'd delete the first one and see if that corrects your issue.

      • Ryu's avatar
        Ryu
        Contributor
        7 years ago

        I actually don't have the second one mapped; I mapped it a few times when the first one broke just to see what was happening, but then I deleted it.  Next time it happens I will try remapping everything to the second one and delete the first and see what happens.