Forum Discussion

mortenb123's avatar
mortenb123
Contributor
30 days ago

TestExecute 15.73 not working: 'Parent object not found'

I upgraded to:

But then my tests fails, It says 'Object not found',

I downgraded backI to:

And it works. This is legacy software I seldom touch. This is the only error I find.

It is unable to find a windows that holds the config. It is in my *.tcNM.
Ind if I use objectspy and click the window it surely says it already exists.

(I do not have it here because I do not have older testcomplete, So I did not save it)

So I'm wondering is there a way to get more info from testexecute runs?
Or a way to traverse the namemapping to see what exists and what do not exists at a given time?

 

 

 file:

Unable to find the following object when executing the Document command:

Aliases.​LraClient.​ConfigViewer.​LraConfigurationContent

 

Reason

The parent object was not found:

Aliases.​LraClient.​ConfigViewer

```

            <Child Name="ConfigViewer" Owner="{00505E49-A1AE-4529-95DF-4557D11BB99C}">
                <Child Name="LraConfigurationContent" Owner="{52BABE78-2C35-49AA-BB88-180AC1FC648F}" />
            </Child>

                            <Child Name="ConfigViewer" Key="{00505E49-A1AE-4529-95DF-4557D11BB99C}">

                                <Properties>

                                    <Property Name="RootVisual.ClrClassName">

                                        <Value Value="Window" />

                                    </Property>

                                    <Property Name="WndCaption">

                                        <Value Value="ConfigViewer*" />

                                    </Property>

                                </Properties>

                                <Children>

                                    <Child Name="LraConfigurationContent" Key="{52BABE78-2C35-49AA-BB88-180AC1FC648F}" ExtendedFind="True">

                                        <Properties>

                                            <Property Name="ClrFullClassName">

                                                <Value Value="ICSharpCode.AvalonEdit.Rendering.TextView" />

                                            </Property>

                                        </Properties>

                                    </Child>

                                </Children>

                            </Child>

```

I'm pretty sure it is the 
What's New in TestComplete 15.73 | TestComplete Documentation

  • Addressed the issue with TestComplete running slow during test playback due to operations using .NET Desktop application

 

7 Replies

  • JDR2500's avatar
    JDR2500
    Frequent Contributor

    15.73 was *not* the best thing ever.  However, 15.74 was just released.  Maybe the Qt bug is fixed in it.  I know it was causing problems for a number of people.

    • pkudrys's avatar
      pkudrys
      Frequent Contributor

      I'm afraid, there seems to be no change with the described "element not found" error in 15.74. I can still reproduce the problem with my simulation project. So we will probably have to wait for another release.   

    • pkudrys's avatar
      pkudrys
      Frequent Contributor

      Hmm, there seems to be no release notes yet? But I'm going to give it a spin. 

  • pkudrys's avatar
    pkudrys
    Frequent Contributor

    Hi,

    The SmartBear folks confirmed that there is a problem in recent TC version. Let's hope for a quick fix ;) 

  • I used https://my.smartbear.com/downloads/TestComplete15XX.exe download and found that 15.71.4.7.x64 works fine while 15.72.x.x do not work. So there are changes between 15.71 and 15.72 that break my object recognition. I just use this version.

    https://support.smartbear.com/testcomplete/docs/general-info/version-history/features-added-to-ver-15-72.html

    Seem to be aligned with pkudrys findings.

    Improvements

    • Qt 6.7 support.
    • The context menu for script tests now contains the “Add to Load Group” option.
    • The summary page now shows the number of actively running load tests.
    • Test execution reports for individual test scripts.

    Bug fixes

    • Fixed the BitBar testTimeout capability and it’s been set to 60 minutes.
    • Addressed the issue with logs not being shown when the TestComplete test adapter does not recognize the newest version on the agent machine.
    • Resolved problems with load tests not being executed in TestExecute.
    • Fixed the message warning users that an item of the same name already exists when adding a test to a Load Group.
    • Addressed the unexpected crash of TestComplete while attempting to rename the Load Group with an invalid character limit.
    • Resolved problems with highlighting objects in the object tree.
    • Fixed the issue with missing detailed information in log files while running TestExecute tests from an Azure pipeline.
    • Changed the wrong timeout on an unsuccessful WaitAliasChild.



     

  • pkudrys's avatar
    pkudrys
    Frequent Contributor

    So I found the reproducible steps and created a ticket. Smartbear folks are looking into it. The workaround is to go back to 15.71. My guess is that they broke it with this fix in 15.72:

    - Changed the wrong timeout on an unsuccessful WaitAliasChild

  • pkudrys's avatar
    pkudrys
    Frequent Contributor

    Hi,

    There is definitely something wrong regarding object recognition in the latest TC version. Our tests (web-based), which worked flawlessly in previous version, started to fail with "element not found" errors, while the element is clearly visible on screen.

    Also, the failing action (typically Click) seems to ignore default timeout and fails well before reaching it. I had to add WaitAliasChild here or there before performing an action on "failing" elements. But this is definitely not acceptable solution. The problem is the random nature of this issue. So while I may add WaitAliasChild on certain actions, it may fail with some other in next run. And so far, I cannot reproduce it with something generic, like SmartBear page, so I have no project to send to support.