Not sure if this will help with the latest windows update, but you might try something similar to how we run TE from powershell.
function closeTestExecute() {
$testExecute = Get-Process TestExecute -ErrorAction SilentlyContinue
if ($testExecute) {
# try gracefully first
$testExecute.CloseMainWindow()
# kill after five seconds
Sleep 5
if (!$testExecute.HasExited) {
$testExecute | Stop-Process -Force
}
}
Remove-Variable testExecute
}
closeTestExecute
...
...
...
$arg1 = "/r"
$arg2 = "/project:$projectName"
$arg3 = "/SilentMode"
$arg4 = "/e"
$arg5 = "/DoNotShowLog"
$arg6 = "/Timeout 7200"
$AllArgs = @($NextTest, $arg1, $arg2, $arg3, $arg4, $arg5, $arg6)
& "C:\Program Files (x86)\SmartBear\TestExecute 12\x64\Bin\TestExecute.exe" $AllArgs | Out-NullHey Carson,
Thanks for your quick reply.
So the issue is not that I cannot close the process, I could close it through powershell at any time.
ussually the machine would pick up the next test once it notices that the TestExecute has finished by for example using:
$processId = start-proces "C:\Program Files (x86)\SmartBear\TestExecute 12\x64\Bin\TestExecute.exe" $AllArgs -PassThru
$processId .WaitForExit()
or
polling every 60 seconds on the procces name of TestExecute and when it doesn't exist anymore starting up the next test.
So the main problem is how to decide when the test is finished if the process doesn't end after running the test.
The timeout parameter could help but the playtimes of the test are variable, and I'm not sure if it would close the program I'll have to try it out.
I cannont find the Donotshowlog parameter in the Testcomplete command line documentation. But the show log at the end of the test is disabled in the project settings. https://support.smartbear.com/testcomplete/docs/working-with/automating/command-line-and-exit-codes/command-line.html
But I think I might still be unclear in what the problem exactly is, I'll try to find a virtual machine where it happens tomorrow and have more screenshots of how TestExecute 11 seems to start closing down and uses very little memory in comparison to when it's runnning the test and then doesn't close down.
A solution I tried out was restarting the ctfmon process every half an hour so I wouldn't have to check which seemed more like a hack than a solution.
If I misunderstood your answer further explanation would be helpful.
greetings and thanks again,
RHendriks
Ah ok, I see what you're saying now, you're never getting an exit code for it. This is likely something to do specifically with the latest update of windows. Do you see this in the latest version of test execute? You might need to talk directly with support on this. Definitely seems like a bug.
