Forum Discussion

Mark_Küpper's avatar
Mark_Küpper
Occasional Contributor
8 years ago

Object recognition broken in TC12 by new "hint"-Feature

Hello,   I am currently evaluating the new TestComplete (Desktop) Version 12.20 (coming from TC V.11.30) and am experiencing trouble migrating my ProjectSuite. The new "Object recognition hint"-Fea...
  • Mark_Küpper's avatar
    Mark_Küpper
    8 years ago

    Well, it turned out that this was the same issue after all, that other posters here had as well.

     

    The problem in my project was the strict behavior control of all routine-chains, meaning that a routine will only execute if its prerequisite-routine returns true (which it doesn't as soon as an uncatched error or warning occurs).

     

    So it seems that this problem doesn't have a (satisfying) solution except maybe waiting for an upcoming TC version while hoping that this feature request will be in it.

     

    Regards

Mark_Küpper's avatar
Mark_Küpper
Occasional Contributor

Thank you for your reply.

 

I have actually already found the first thread of the ones you posted, however it is not the same problem.

 

My Problem isn't just a cosmetic issue. The Object, that the hint-message says was not found, should have been found and was indeed found by the older TC-Version.

 

To be sure, I just started both, TC11 and TC12 with two copies of the same ProjectSuite.

I then executed a routine, that calls a row count method on a winforms table (the tested app is started on the same machine).

 

In TC11 the Routine worked as expected. TC12 showed the hint-warning and was not able to call the method on the exact same tested app which was also not restarted between this test. There is definitly something odd about the object recognition..

 

I really hope, that there are more suggestions.

 

Regards

tristaanogre's avatar
tristaanogre
Esteemed Contributor
8 years ago

Double check timing.  On your project, there is an Auto-Wait Timeout property in Tools | Current Project Properties | Playback.  By default, for new projects, that's 10 seconds.  It COULD be that this needs to be increased.  Try taking it up to 20000 ms and see if that corrects your problem.

 

Converting from TC 11 to TC 12 SHOULD be seemless but it's possible that this value might have gotten reset.

  • Mark_Küpper's avatar
    Mark_Küpper
    Occasional Contributor
    8 years ago

    I just tried taking up the project wide auto-wait timeout to 20000ms (in addition to doing the same to the individual operation, which I already tried before).

     

    Still no good.

     

    I still think, that the problem has something to do with the multiple mapped instances of the same object who share the same identification criteria with only the index property to differentiate between them (see also screenshot and description of my first post).

     

    Regards

    • tristaanogre's avatar
      tristaanogre
      Esteemed Contributor
      8 years ago

      Indexes are a valid way of identifying objects.  However, the index on a process is not a static index.  If there are two processes with the same name, it depends upon which one is first in the Z-order in the OS as to which one gets Index 1 and which one gets Index 2.  This index will actually change back and forth as the applications are interacted with.  

       

      This is probably at the root as to why you're getting the hints you're getting.  I'm not sure why the behavior of your tests changed from TC 11 to TC 12 but it's always tricky trying to interact with two instances of an application at the same time.  If there's something like a command line switch or something that would be able to distinguish the two, that would be better than index anyways.

      • Mark_Küpper's avatar
        Mark_Küpper
        Occasional Contributor
        8 years ago

        Well, it turned out that this was the same issue after all, that other posters here had as well.

         

        The problem in my project was the strict behavior control of all routine-chains, meaning that a routine will only execute if its prerequisite-routine returns true (which it doesn't as soon as an uncatched error or warning occurs).

         

        So it seems that this problem doesn't have a (satisfying) solution except maybe waiting for an upcoming TC version while hoping that this feature request will be in it.

         

        Regards