Forum Discussion

cam_farineau's avatar
cam_farineau
Contributor
8 years ago

Start TestExecute from TeamCity

Hi,   To test our desktop application we have a Master project that runs the Slave project on different VMs. The Master project is started on a Management machine. We are currently moving our Buil...
  • cam_farineau's avatar
    cam_farineau
    8 years ago

    I figured it out.
    My problem was that I didn't disable "uiAccess" in the "TestExecute.exe.manifest".

     

    <security>
        <requestedPrivileges>
            <requestedExecutionLevel level="asInvoker" uiAccess="false"/>
        </requestedPrivileges>
</security>

    So the Desktop interaction was needed according to the Manifest of the app.

     

    With this attribute to false, TE doesn't require a Desktop / UI Access. So I can start my test directly from TeamCity and this domain system account without interaction with the Desktop.

     

    Thank you all for your help !! 

     

AlexKaras's avatar
AlexKaras
Champion Level 3
8 years ago

Hi,

 

As is said on the pages that Marsha provided references to and have been discussed here a lot of times:

-- GUI application in the Windows environment *must* have active interactive session in order to be able to display its UI. This is required by OS, but not by TestComplete. Note, that active interactive session is not the same as allowance to the service application to interact with the desktop.

 

In order to test GUI application with any tool (Selenium/QTP-UFT/Ranorex/CodedUI/TestComplete/etc.) you *must*:

-- Provide active interactive session for your application;

-- Start your tested application in this session;

-- Start your test tool in the same session and start tests;

-- Keep session open and not locked until tests finish.

 

One more link that might help: http://smartbear.com/forums/f55/t77736/Running-TestComplete-scripts-from-TeamCity-Agen.aspx

  • cam_farineau's avatar
    cam_farineau
    Contributor
    8 years ago

    Thank you for your answer,

     

    But we are not running any tests on this machine. 
    We want to run our Master project from TeamCity running as a service on this machine. This Master project doesn't require interaction with the Desktop, it is not testing our App.

    This project will start the Slave remote project (actual UI tests of our app that require Desktop Interaction) on different VMs through TestExecute directly.

     

    So we juste need a way to start the Master from TeamCity, in the background or any other way... Thereby it can launch our actual UI automation tests on VMs using TestExecute.

     

     

    • AlexKaras's avatar
      AlexKaras
      Champion Level 3
      8 years ago

      Hi,

       

      Actually, TestExecute does not require interactive user session and can execute test code without any problem if interaction with GUI is not required. So your scenario should work.

      My guess is that the error from your initial post caused not by TestExecute itself, but, maybe, by the failed command (PSSession) that was executed previously.

      • cam_farineau's avatar
        cam_farineau
        Contributor
        8 years ago

        Hi,

         

        No this issue is cause by TestExecute itself. 
        I tried to start from the account that is using TeamCity directly and with a PSSession from a normal user account but I get this exception everytime. It seems that TE requires this "interactive window station"

        So what do you mean when you said TestExecute does not require an interactive user session ?