Forum Discussion

Hema_Naik's avatar
Hema_Naik
New Contributor
8 years ago
Solved

Test Complete 12 issues with Windows 10.

Hi,   Recently I have made changes I am facing issue with the Test Complete latest version 12 newly installed on Win 10 version. I am constantly facing 4 issues with latest changes in OS and TC la...
  • tristaanogre's avatar
    tristaanogre
    8 years ago

    It looks like there are a couple of problems happening.

     

    First of all, it appears that, on the failed tests, there are a lot of object recognition errors. Secondly, there is a warning indicating something about the number of instances of the application under test. It's possible, it seems, that you might be not properly closing your application under test after each project run which will result in these kinds of errors. Double check your tests you are executing and make sure that after each test run, you are doing any "clean up" work that needs to be done to prepare your environment for the next run. One possible thing is that you are doing the clean up work but there may be a delay in the actual shutdown of AVM5 so that, when the next test starts, it hasn't fully shut down from the previous run.

tristaanogre's avatar
tristaanogre
Esteemed Contributor

Can you make sure you're running TC as an administrator? I believe that is something that is necessary in order to do some of the low-level stuff that TC needs to do within the operating system.

Hema_Naik's avatar
Hema_Naik
New Contributor
8 years ago

Hi,

I have executed my test scripts as an Administrator. Its still the same.

Screenshot is provided for reference.

Please suggest any settings missing in TC 12 or any changes to be made with Windows 10 ?

 

Thanks,

Hema

 

  • tristaanogre's avatar
    tristaanogre
    Esteemed Contributor
    8 years ago

    It looks like there are a couple of problems happening.

     

    First of all, it appears that, on the failed tests, there are a lot of object recognition errors. Secondly, there is a warning indicating something about the number of instances of the application under test. It's possible, it seems, that you might be not properly closing your application under test after each project run which will result in these kinds of errors. Double check your tests you are executing and make sure that after each test run, you are doing any "clean up" work that needs to be done to prepare your environment for the next run. One possible thing is that you are doing the clean up work but there may be a delay in the actual shutdown of AVM5 so that, when the next test starts, it hasn't fully shut down from the previous run.

    • Hema_Naik's avatar
      Hema_Naik
      New Contributor
      8 years ago

      Hi,

       

      The feedback was helpful. Found problem with delay in the actual shutdown of AVM5. Introduced OnStop event for those scripts. Working fine.

       

      Thanks for the help!

      Hema