Forum Discussion

rickm's avatar
rickm
Contributor
9 months ago

Searching for the mapped object "btnYes" took a long time

I've been running TestComplete for 13 years now. I have over 1100 tests, all created with the recording function and letting TC take care of all name mapping. This is with an Open App. Nothing browse...
  • rickm's avatar
    rickm
    9 months ago

    I eventually convinced myself that the problem was indeed that the problematic buttons were not _missing_ any mapping, but TC simply mapped them into the wrong place in the Mapped Object list. These maps were created over 10 years ago, obviously with a very old version of TC.

    I couldn't see any way to edit the mapping (just search criteria), so I deleted the 3 buttons from the main program parent in the Mapped Objects (including their aliases). Then I recorded a little keyword test using the 3 buttons to force TC to create new maps. The new maps went into the correct object, the same as the other buttons that do behave properly, and the problem is solved!

    Thanks to all, I sincerely appreciate the help. 

rraghvani's avatar
rraghvani
Champion Level 3
9 months ago

Where does the 'Yes' button appear in the Object Browser, hierarchy tree? How many levels down, is it?

  • rickm's avatar
    rickm
    Contributor
    9 months ago

    The buttons appear right at the top of the Object Tree in the Object Browser at the first level below the main program, exactly as in the Run Code Snippet call that runs in a fraction of a second. The only Button that shows there at any time is the one that is active on the screen at the time.

     

    v Process("MyApp")

       v Window("#32770", "MyApp", 1)

          v Window("Button", "&Yes", 1)

     

    The Object Spy shows the FullName as this hierarchy which is what works in Run Code Snippet, and shows the Name as Windows("Button", "Yes"", 1), but the MappedName is Aliases.MyApp.dlgMYAPPError.btnYes. The Object name dlgSTRIPLOGError doesn't appear in the Object Tree anywhere. It seems like the mapped name should somehow point to "#32770"?

     

    In the Workspace "NameMapping" tab, in its top section "Mapped Objects", it shows as "NameMapping.Sys.MyApp.btnYes", but below in the Aliases section it appears under "dlgMYAPPError". No mention of #32770 anywhere, but the context menu "Show in Object Browser" in both the top and bottom section of NameMapping find it at the top of the Object Browser.

    • rraghvani's avatar
      rraghvani
      Champion Level 3
      9 months ago

      If you are using name mappings, then it's important to get the name mappings correctly defined, to instruct TestComplete on how to locate the object in your tested application.

      If you have the following hierarchy defined in TC,

      • Mapped Object: Sys.Process("MyApp").Window("#32770", "MyApp", 1).Window("Button", "&Yes", 1)
      • Aliases Mapped Object: Aliases.MyApp.dlgMYAPPError.btnYes

       

      Then the following aliases should equal to,

      • MyApp = Process("MyApp")
      • btnYes = Window("Button", "&Yes", 1)
      • dlgMYAPPError = Window("#32770", "MyApp", 1) - my guess is, this is not correctly defined.

       

      • rickm's avatar
        rickm
        Contributor
        9 months ago

        You have the same mapping for btnYes and dlgMYAPPError. Did you mean to write 

        btnYes = Window("Button", "&Yes", 1)