Forum Discussion

cpop's avatar
cpop
New Contributor
11 years ago

TestExecute suite runs in remote session but not in vSphere client console

Hi,



I have a test that successfully runs using test execute on a 2008x32 Server remote session. However, when I run it from the vSphere client console it starts and all goes well until it opens a popup and tries to click a button. It does not find the control.

Why would that be? Did anyone have this problem before?



Thanks,

Cristina
  • jose_pita's avatar
    jose_pita
    Super Contributor
    11 years ago
    Hi Cristina,



    When you say you run it through a console, do you actually have an UI present or just the console? Can you see TE executing the clicks and navigation?
  • cpop's avatar
    cpop
    New Contributor
    11 years ago
    Hi Jose,



    Yes, I have UI to the console and I can see the test executing up to where it refuses to continue. I also had it run without having an UI (open session to it) and got the same result.



    I believe it is a screen resolution problem. I have button controls that are contained inside a ribbonBar, that the tool does not see individually; I use fixed coordinates inside the ribbonBar to click the buttons. Looking at the log and screenshots from runtime the button is not clicked.

    I maximize my test frame at the beginning of the test to avoid coordinates issues and it works on a Win7x64 OS but I see that on the 2008x32 server my maximized test frame is smaller than usual.



    Is there a way to avoid this?



    Thanks,

    Cristina
  • TanyaYatskovska's avatar
    TanyaYatskovska
    SmartBear Alumni (Retired)
    11 years ago
    Hi Cristina,

     


    I suggest that you check how exactly you obtain the opened pop-up in your test. On different computers, it can take TestComplete different time to fully recognize this pop-up. That's why, the test passes on one computer and may fail on another one. So, it's better to use WaitWindow (or another Wait method) to obtain the control and only after that click a button inside.

  • hlalumiere's avatar
    hlalumiere
    Regular Contributor
    11 years ago
    Make sure your VMWare Tools are up to date. If this is a VM you migrated to vSphere from VMWare Workstation, you need to reinstall VMWare Tools from scratch. Other than that I don't see anything else... I run all my tests on 45 VMWare ESXi VMs, and vSphere console (through the VMRC API) is the only way I access them.