Forum Discussion

Thanh's avatar
Thanh
Occasional Contributor
10 years ago
Solved

Is there a command or way to run a test without needing to RDP into test computer?

Hello everyone. We are in a process of automating our application deployment so now we are able to automatically uninstall old builds and install new builds as well as pulling latest TC codes from source control. I would now like to automate the starting of test also. Currently I need to manually RDP into each test machine and start the test from each one using TE. 

 

To clarify. The deployment automation has been written in powershell

 

I want to know if there is a command or method of starting a test where I don't need to RDP in? Does TC really need to have a RDP window?

 

I hope I have explained it clearly. 

 

Thanks for any help in advance. 

5 Replies

  • Colin_McCrae's avatar
    Colin_McCrae
    Community Hero
    10 years ago

    It doesn't need RDP.

     

    It needs an active user session.

     

    Can be started via command line (so BAT file or whatever) which your build/CI process should be OK with. Just ensure that whatever it starts it on has an active user session.

     

    Command line: https://support.smartbear.com/viewarticle/69415/

    (Much the same for TestExecute)

     

    User session errors: https://support.smartbear.com/viewarticle/76957/?FullScreen=1&ShowTree=0

     

    I've had everything run automatically as part of CI. I was lucky as the build engineer here was already familiar with GUI automation software and their need for an active user session. 

    • AlexKaras's avatar
      AlexKaras
      Icon for Champion Level 1 rankChampion Level 1
      10 years ago

      Colin_McCrae:

      Hi Colin,

       

      Out of curiosity: what CI are you using?

      The reason for the question is that I was more than happy with SmartBear's AutomatedBuildStudio (ABS) until it was discontinued for some reason. I had some experience with TeamCity and Jenkins, but both of them... not miles, but light-years away from ABS in terms of convenience for CI engineer. (Presentational part is not bad and, maybe, it is not bad for Java projects as well - just have no experience with this. But for everything else - it's a nightmare.)

      All other build/CI products are mentioned less frequently than TC and Jenkins and that is why I am wondering. (I liked to do CI tasks with ABS, but I am trying my best to avoid them as much as I can for TC / Jenkins. :) )

      • Colin_McCrae's avatar
        Colin_McCrae
        Community Hero
        10 years ago

        Not really my area Alex, I just slot my part in.

         

        When being triggered against nightly builds, it was almost entirely TeamCity doing the work as far as I know.

         

        Repo's were in Git. TeamCity was configured to run the nightly build, install it, pull down the latest test script + test packs from Git. It then triggered the test. My setup makes this simple as it ALWAYS simply runs the "Driver" module. What runs after that is entirely determined by the contents of the test packs pulled down.  My tests write out a small HTML file on completion which TeamCity picks up. This contains the headline results figures and a link to the main results (stored on a network drive ... all in my own formats) which were presented on the TeamCity page.

         

        TFS is now part of that mix as well. But I'm not too up on exactly where it slots into things. It varies by project where I work and I'm working on legacy Delphi stuff at the moment which is not a project currently run through TFS.