Forum Discussion

krkarthik_info's avatar
krkarthik_info
Frequent Contributor
6 years ago
Solved

Sys.Process("rundll32") is not shown in object browser

Hello Everyone,   I am having a dialog box with two controls say Buttons Yes an No.   When I spy the buttons, testcomplete identifies it. But when I try to run as a test to perform Click acti...
  • krkarthik_info's avatar
    krkarthik_info
    6 years ago

    All, 

     

    I have upgraded my TestComplete version from 12.0 to 14.0, and with the latest version I am able to click on the buttons successfully and the dialog disappears.

     

    I am really not sure what was the problem with TC 12.0, luckily TC 14.0 helped me out of the problem.

     

    Thanks,

    Karthik K R

krkarthik_info's avatar
krkarthik_info
Frequent Contributor

Hi Tanya,

 

Second question not resolved yet. Still the issue exists.

 

Thanks,

Karthik K R

tristaanogre's avatar
tristaanogre
Esteemed Contributor
6 years ago

If there is more than one Sys.Process("rundll32"), then it should have an index.  Sys.Process("rundll32", 2) and so forth.  You need to make sure that you are referencing the correct process before you try to click on the dialog.

  • krkarthik_info's avatar
    krkarthik_info
    Frequent Contributor
    6 years ago

    Hi Robert,

     

    Object Browser shows only one running process of Sys.Process("rundll32") and I am making action (Like Clicking) on the correct dialog. Even TestComplete Log shows it performed the action correctly. It dint throw any ambiguos object recognition error message too.

     

    Please see the below image

     

    Even after clicking the button, the dialog remains same on the screen. But when I do manual click on No button, the dialog disappears. Expected the same behavior while running through TestComplete.

     

    Thanks,

    Karthik K R

    • tristaanogre's avatar
      tristaanogre
      Esteemed Contributor
      6 years ago

      Is there more than one instance of WIndow('#32770')?  That could also be part of the issue.

       

      Also... could be timing... while the window may be up and clicked on, there may be something else going on where the click is not recognized, some sort of background processing temporarily disabling the button.  Have you tried, just for debugging purposes, putting a hard coded delay before the button click?

      • krkarthik_info's avatar
        krkarthik_info
        Frequent Contributor
        6 years ago

        I have verified that only one instance of window("#32770") appears in the object browser. Also I have tried giving some hard coded delays, unfortunately this too didnt work.

         

        Thanks,

        Karthik K R