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?

     

rraghvani's avatar
rraghvani
Champion Level 3
3 years ago

Launch PowerShell command prompt and type in 'testexecute'. If you get an error, then you'll need to set your environment path variable e.g. $env:Path += ';C:\Program Files (x86)\SmartBear\TestExecute 15\x64\Bin;' (include this in your .ps1 file). Type in 'testexecute' again, and it should launch.

 

Exit TestExecute, now try your Schedule Task again.

 

FYI, the instructions I've given, are the ones that I use on my VM.

  • dhundley's avatar
    dhundley
    Regular Contributor
    3 years ago

    if i bring up the powershell command prompt and type in TestExecute it launches TestExecute. i get an error popup about it not specifying a valid project suite or project but powershell knows about testexecute. remember, if i run the powershell script manually (with the start-process statement that you provided) it does work. the problem is getting Task Scheduler to run it. also, as i've already said before. i have another scheduled task that is triggered at system start up which also runs powershell to send an email and that works also. so task scheduler know how to run powershell. i just can't figure out why task scheduler is having an issue with the start-process cmdlet in powershell. 

     

    i really appreciate your effort but i feel like we keep going over ground that has been covered before instead of trying something new. as i said, i'll keep after it and post the resolution when/if i ever come up with something. i'm guessing it's something weird with the VM and i'm asking our support help desk guy who set the VM up for me if he's got any ideas. thanks again!