Forum Discussion

edtan's avatar
edtan
New Contributor
6 years ago
Solved

Sys.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 ...
  • tristaanogre's avatar
    tristaanogre
    6 years ago

    In re-reading your post, you're using the "Find" method and using the "Name" property of the object to find what you're looking for.

    Name is not a recommended property to use, to be honest. A better way would be to examine the object and pick a set of properties that uniquely identify it.  You can then pass them as arrays to the find object.

asmatullah's avatar
asmatullah
Contributor

Hi ,

I used to get problem to recognise the VCLObjects .

Some times I even gets objects with T prefix. I tried launching the application with TestedApps and with sufficient delays. Also I am using Namemapping. Now I can see the test running properly.

 

edtan's avatar
edtan
New Contributor
6 years ago

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.

  • tristaanogre's avatar
    tristaanogre
    Esteemed Contributor
    6 years ago

    You will lose performance using "Find" instead of NameMapping.  The Find methods are pretty performance taxing as they need to do a scan of the object tree via the code engine where as the NameMapping engine is built in and optimized.

    Is there a reason why you are bypassing the NameMapping?

     

    As for your questions:

     

    1) Are you running with debug info agent against your Delphi application?  If so, that does cause a bit of a start up delay as it needs to read the info in.  

    2) Not entirely sure why this is the case, but my guess from working with other desktop applications is that there are processes in the application that need to complete before the components can be recognized.  I'm assuming the object is there, just not showing as "VCL(blah)"?  

    You can try using FindEx (I think this is available in TC 11).  This does the find with a timeout delay that you can tell it to try and find the object within a certain time period.

    • AlexKaras's avatar
      AlexKaras
      Champion Level 3
      6 years ago

      ... and to add to Robert's reply:

      It is recommended to use not Namemapping in your tests, but Aliases.

       

    • edtan's avatar
      edtan
      New Contributor
      6 years ago

      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).

      • tristaanogre's avatar
        tristaanogre
        Esteemed Contributor
        6 years ago

        In re-reading your post, you're using the "Find" method and using the "Name" property of the object to find what you're looking for.

        Name is not a recommended property to use, to be honest. A better way would be to examine the object and pick a set of properties that uniquely identify it.  You can then pass them as arrays to the find object.