Forum Discussion

jkrolczy's avatar
jkrolczy
Regular Contributor
7 years ago
Solved

TC 12.40 x64 Object recognition issue with Window("WindowsForms10.Window.9.app. ...

I am trying to be sure/get my currently fwk/scripts to work on TC12.40 x64 to use the benefits provided,

but when running TC12.40 x64 my windows appl.

 

WindowsForms10 is not being recognized correctly.

 

Curious to see if others are starting to have this issue as well and TC12.40 x64 ramp up in use?

 

I can open the same auto fwk project code up in TC12.40 x86 and all is fine.

 

I have not changed any settings, I would think I should not have to if one way works (x86)

and the other way (x64) does not.

 

I know there are probably x64 bugs to work out.

 

 

Regards,

James K

  • Past use of TestComplete x86, I have always Run As Administrator, for TestComplete to access
    what it needs from the computer and application.

     

    So with the install of TC 12.40, the x64 .exe was not set to Run As Administrator

    as the TC 12.40 x86 already had been set from TC 12.31 x86.

     

    With TC 12.40 .exe x64 set now to 'Run As Administrator', the problem has been resolved.

     

    The Application is being recognized like it should be.

     

     

    Thanks for the suggestions to check you provided SmartBear.

     

    Regards,
    James K.

     

2 Replies

  • tristaanogre's avatar
    tristaanogre
    Esteemed Contributor

    Have you checked the object browser for the component in both versions and looked for a difference?  If so, this might be able to be resolved with "conditional mapping" to do an either/or on a property value

  • jkrolczy's avatar
    jkrolczy
    Regular Contributor

    Past use of TestComplete x86, I have always Run As Administrator, for TestComplete to access
    what it needs from the computer and application.

     

    So with the install of TC 12.40, the x64 .exe was not set to Run As Administrator

    as the TC 12.40 x86 already had been set from TC 12.31 x86.

     

    With TC 12.40 .exe x64 set now to 'Run As Administrator', the problem has been resolved.

     

    The Application is being recognized like it should be.

     

     

    Thanks for the suggestions to check you provided SmartBear.

     

    Regards,
    James K.