Forum Discussion

dhundley's avatar
dhundley
Regular Contributor
3 years ago

powershell equivalent of running testexecute with command line arguments

in the SmartBear support documentation is this site https://support.smartbear.com/testcomplete/docs/working-with/automating/command-line-and-exit-codes/command-line.html   that shows how to run...
  • rraghvani's avatar
    rraghvani
    3 years ago

    This is the PowerShell command that I use,

     

    Start-Process 'C:\Program Files (x86)\SmartBear\TestExecute 15\x64\Bin\TestExecute.exe' -ArgumentList """C:\Sandbox\TestComplete\Proj\Proj.pjs"" /run /exit /DoNotShowLog /ExportLog:""C:\Sandbox\Log\index.html"" -Wait

     

    Make sure you use the correct single and double quotes.

  • rraghvani's avatar
    rraghvani
    3 years ago

    The properties for my task schedule looks like,

     

    Username shown, has full admin access.

    I've shown you the commands that I use

     

     

    History showing completed task schedules

     

    Try to schedule a task for .ps1 script that contains only,

     

    Write-Output 'Testing schedule task'

     

    And if that doesn't work, then does the History tab show anything?

     

Kitt's avatar
Kitt
Regular Contributor

dhundley did you try -Verb RunAs as I posted earlier? Are there any errors when running the scheduler?

dhundley's avatar
dhundley
Regular Contributor
3 years ago

i have tried adding -Verb RunAs to the arguments in Task Scheduler and then also adding -Verb RunAs onto the start-process line inside the ps1 script that attempts to run TestExecute. neither way appears to work for me. i can run the powershell ps1 script manually from the ISE and it works just fine. i've also tried to changing the user that runs the scheduled task from the logged on user (which is what works manually) to SYSTEM. that doesn't work either. i found an online article (https://techgenix.com/how-to-schedule-powershell-scripts/) that suggests you can use powershell cmdlets to schedule it to run but i'm not very familiar with those so i'm still hoping to get Task Scheduler to work if possible

  • Kitt's avatar
    Kitt
    Regular Contributor
    3 years ago

    You could try a batch file instead of PowerShell. And also, to run the task with the option "Run whether user is logged on or not" you have to activate the option "Run with highest privileges". - so check that you have that set up correctly before attempting the batch approach. And if you still have issues, try [this post] .

     

    If there are any UAC restrictions, you can also attempt to bypass them using "-ExecutionPolicy ByPass".

    • dhundley's avatar
      dhundley
      Regular Contributor
      3 years ago

      i have also tried a bat file. again, when i run it manually it works perfectly. when it is called from task scheduler it doesn't work. i will give your bypass suggestion a try and let you know if that helps any.