Forum Discussion

gehrig44's avatar
gehrig44
Occasional Contributor
16 years ago

Objects in remote IExplore.exe process not found

If I run my project locally everything runs fine (TestComplete or TestExecute).  However, when I run mt project via TestExecute command line through a remote session, iexplorer is started in that session, but none of the objects are found in iexplorer.  



This has been terribly difficult to troubleshoot since I can't actually see what is going on.  However, I can open TC up on that system after the run and see the iexplore.exe process does exist..and has the correct user associated with it.    The log even shows that it navigated to a URL correctly.  But, once it tries to interact with an object in the page, it can't find it.  Also, my visualizer screenshots are just white.



I set iexplore.exe as a testedapp and used the runAs login credentials with no luck.  The user is a system admin.   Basically I am only able to run my tests locally atm :(









 

6 Replies

  • gehrig44's avatar
    gehrig44
    Occasional Contributor
    16 years ago

    Here is an update on my situation.  My problem now is that I can get Iexplore to the IsOpen = True state even though I can see it.





    I am executing my project using TestExecute remotely with PSExec.exe. I am logged into the remote machine with the same account to watch what is happening.  I can see TestExecute run and Internet Explorer open, but TestExecute cannot find any objects in iexplore.  When I open TestComplete, I can see the iexplore process with object explorer, but it is IsOpen = False.  The username associated with the process is correct.  The username is an admin account.


    I tried having iexplore open via my TestComplete project, but it does the same thing.  Both RunAs and Simple.


    If I run the project on the machine locally, it runs fine. 


    Here is the command used to remotely run TestExecute.


    <command line removed>

  • Pakema's avatar
    Pakema
    Contributor
    16 years ago
    Hello Edward Ecklund!



    Do you know that for work with gui app via automation tool in remote / local machine YOU need run it when you see it? BECAUSE via cmd,f.e. psexec (it's not stable program, best way write self small code on WMI), YOU can test ONLY interactive program and all. Some cmd command, f.e. dir, md, cd, copy etc



    For resolve you problem - test and run your test via RDP. This is best way too.



    GL HF :)


  • Dmitry_Nikolaev's avatar
    Dmitry_Nikolaev
    Icon for Staff rankStaff
    16 years ago

    Hi Edward,





    Nikita is right, the problem is that the remote system does not have a GUI, and therefore, TestExecute cannot interact with it. You can find information on this situation in the Running Tests on Locked Computers help topic.





    You need to use the Network Suite feature to run remote tests without any problems. Information on this feature can be found in the Distributed Testing help topic.
  • gehrig44's avatar
    gehrig44
    Occasional Contributor
    16 years ago
    It looks like the NetworkSuite method needs to run the project via TestComplete, not TestExecute.  This wouldn't work, since we paid for specific number of floating licenses for development.



    I'll try to execute from Remote Desktop instead.  Which means I should really just move the the builder program that executes TestExecute to a system other than the one TestExecute is going to run on.  Because, I don't see how I can remote desktop, since it is already on that system.
  • gehrig44's avatar
    gehrig44
    Occasional Contributor
    16 years ago
    Also, can a mod please remove the psexec line I posted earlier?  I shouldn't have posted that.
  • Dmitry_Nikolaev's avatar
    Dmitry_Nikolaev
    Icon for Staff rankStaff
    16 years ago

    Hi Edward,





    Please note that the master project can be executed by TestExecute. There is no a requirement to use TestComplete.





    I have removed the command line from your post.