Forum Discussion

dhundley's avatar
dhundley
Regular Contributor
2 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
    2 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
    2 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?

     

rraghvani's avatar
rraghvani
Champion Level 3

Oops, sorry about that dhundley Correct command is,

 

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

 

On the VM, create a file called e.g. AutomateTC.ps1 with the above command. Create a task schedule and the program/script to run is C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe (location of your powershell.exe) followed by arguments -WindowStyle Minimized -File C:\Sandbox\AutomateTC.ps1 (window style minimized is optional; location of your .ps1 script) and start in %HOMEDRIVE%%HOMEPATH% (optional)

While on the VM, if you right click the scheduled task you've added, select Run, it will run TC.

 

The above will work, providing the user is logged on to the VM and the session is active. You will most likely want to run the scheduled task without having to be logged on to the VM, therefore, you'll need to use SessionCreator.

dhundley's avatar
dhundley
Regular Contributor
2 years ago

i have another ps1 file on the same VM that is also run as a scheduled task and it works just fine.  all I have in its program/script box for the Action in Task Scheduler is "powershell.exe" (not the entire path). rather than containing a start-process statement, all that ps1 file has in it is a Send-MailMessage, the Arguments box has the -file switch and the fully qualified pathname and file of the ps1 file and does not have a -Verb RunAs argument.  Rather than having a scheduled start time it is triggered when the computer starts. As I said, it runs perfectly

 

for this scheduled task the ps1 file has the start-process statement for running testexecute and I have coded it just as your recommended. i think i already mentioned that if i manually run the powershell from the ISE it completes successfully. TestExecute starts up, runs the project/unit/script and then closes. For some reason though it is not working when the task scheduler job tries to run it and I am logged on and watching it. it doesn't even fire up TestExecute. I've tried putting the -Verb RunAs on the start-process line and that doesn't help either. I've also tried bypassing the execution policy but that didn't work. 

 

Clearly this is not an issue with TestExecute nor is there a problem with how I have written the powershell script (since it works when i run it manually) but rather there is something wonky about Task Scheduler or possibly about the VM itself. I will continue to work on it and if i ever get it running i will come back here and post the solution. Thanks for all your help.