Contributions
Re: Sys.Refresh() prevents Window object from being recognised as VCLObject
Thanks for the reply. I'm looking at bypassing using Find methods to bypass NameMapping/Aliases so the tests can adapt to changes in the app with minimal changes (as the app is still under development). Follow up to your answers: 1) I was originally running with debug info agent enabled. However I tried disabling it and saw no difference in the time it took to recognise the VCLObject. 2) Yes, the object is there - but it is recognised as a Window object rather than a VCLObject. I've also tried using FindEx, but setting Refresh = true causes the Window object to never be recognised as a VCLObject (same effect as using Sys.Refresh() or Refresh = true on the Find method).2.6KViews0likes2CommentsRe: Sys.Refresh() prevents Window object from being recognised as VCLObject
Thanks for the replies. Yes, the main window is name mapped. However, I am not accessing the object via it's mapped names. Instead, I am using the Process.Find method on the Name property to find and access the VCLObject since I am trying to remove the dependency on NameMappings.2.6KViews0likes5CommentsSys.Refresh() prevents Window object from being recognised as VCLObject
Hi, The Delphi application I am testing starts with this flow: Splash screen -> login screen -> main window. The main window is represented as a Window object in the object browser and is available at launch.However it only gets recognised as a VCLObject once the login screen appears (~20 secs later on my machine). I've observed this behaviour both from launching the application manually and launching it as part of a test script using TestedApps.Run. The issue is when Irefresh the object tree programatically before the login screen appears, either using Sys.Refresh() or Process(..).Find with the refresh parameter set to true, the main Window object never gets recognised as a VCLObject. However, if I pause test script execution and refresh the object tree manually in the Object Browser, the VCLObject sometimes appears. When it doesn't appear, I need to either highlight the window by right clicking the Window object and selecting "Highlight on screen", or by inspecting the window using the Object Spy. Refreshing the object tree after performing either of these actions causes the VCLObject to appear. So my questions are: What can cause the Window object to take so long to be recognised as a VCLObject? Why does programatically refreshing the object tree cause the Window object to never be recognised as a VCLObject? I am using TestComplete 11.31.2420.7 on Windows 7. Any advice or help is appreciated. Thank you.Solved2.7KViews0likes8Comments