Forum Discussion

jlehoang's avatar
jlehoang
New Contributor
23 days ago

Issues with Running TestExecute in Powershell

I'm trying to run TestExecute using powershell, and it seems to startup, but then it returns to the command input shortly after without running my test suite. I've tried running it on command  line, and it seems to work just fine, so I feel like there is something that is not being transferred correctly in the powershell format: 

 Start-Process -FilePath $testExecutePath -ArgumentList $pjsFilePath, "/run", "/project:$projectName", "/test:$TestGroupName", "/ErrorLog:.\ErrorLog.log", "/SilentMode", "/exit", "/AccessKey:$accessKey" -Wait

I've tried running different versions from related community support posts with not much success.

Command Line

3 Replies

  • rraghvani's avatar
    rraghvani
    Icon for Champion Level 3 rankChampion Level 3
    22 days ago

    Your command line is incorrect. I suggest you see TestExecute Command Line and make note of how parameters are used and passed to TestExecute. 

    I suggest you don't use Start-Process and use the full path to call TestExecute.exe

    Also, we can not see what values are passed in, i.e. into $testExecutePath and other values.

    • jlehoang's avatar
      jlehoang
      New Contributor
      22 days ago

      I am using the documentation guide for the parameters. If I replaced this path with the TestComplete.exe path, my tests will run using the TestComplete.exe command-line run, which the parameters seem the same to me for the most part between the two unless I am missing something? 

      Also if I take the same string and run it into Command Prompt, it seems like TestExecute.exe works just fine. 

      • rraghvani's avatar
        rraghvani
        Icon for Champion Level 3 rankChampion Level 3
        22 days ago

        Command line parameters are not separated by commas. Same applies to PowerShell.