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

tristaanogre's avatar
tristaanogre
Esteemed Contributor

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