Contributions
Re: Starting Testexecute with powershell hanging process windows update 1803
Hey 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 anymorestarting up the next test. Sothe 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, RHendriks3.3KViews0likes1CommentStarting Testexecute with powershell hanging process windows update 1803
Hey, I encounter a problem using testexecute after an update of windows Problem: The process TestExeute.exe keeps runnning after the test has finished. The powershell script that is waiting for the process to finish never continues and gets stuck. The test is started on a windows 10 (build 17134) machine with TestExecute 11 on itusing the following command: Start-Process "C:\Program Files (x86)\SmartBear\TestExecute 11\Bin\TestExecute.exe" -ArgumentList '"C:\PAthToTestPRoject\TestProject TEST.pjs" /project:"TestProject TEST" /test:"Script|TestCentrum|TestCentrum_Main" /r /e /SilentMode /ForceConversion' This script has worked until we installed the windows update 1803. After rebooting the virtual machine and starting an instance of testcomplete or testexecute a edge browser would start. I followed the advice on the forum to not enable support for microsoft store apps. the Edge browser didn't start anymore but the TestExecute process still didn't always close at the end of the test. What I have found so far: I found a process cftmon.exe that when I analyse the wait chain it's waiting for the testeExecute proces. in the testexecute proces it says it's waiting for cftmon.exe. when I kill the cftmon.exe process it restarts immidiatly and the testexecute process is closed.3.3KViews0likes7CommentsRe: Starting Testexecute with powershell hanging process windows update 1803
Hey, Problem: The process TestExeute.exe keeps runnning after the test has finished. The powershell script that is waiting for the process to finish never continues and gets stuck. The test is started on a windows 10 (build 17134) machine with TestExecute 11 on itusing the following command: Start-Process "C:\Program Files (x86)\SmartBear\TestExecute 11\Bin\TestExecute.exe" -ArgumentList '"C:\testprojectPath\TestProject TEST.pjs" /project:"TestProject TEST" /test:"Script|TestCentrum|TestCentrum_Main" /r /e /SilentMode /ForceConversion' This script has worked until we installed the windows update 1803. After rebooting the virtual machine and starting an instance of testcomplete or testexecute a edge browser would start. I followed the advice on the forum to not enable support for microsoft store apps. the Edge browser didn't start anymore but the TestExecute process still didn't close at the end of the test. This would happen sometimes, there have been times that I was able to interupt the test and it would close the process. What I have found so far: I found a process CFTmon.exe that when I analyse the whaitchain says it's waiting for the testeExecute proces. in the testexecute proces it says it's waiting for CFTmon.exe. when I kill the CFTmon.exe process it restarts immidiatly and the testexecute process is closed. I hope I was clear in my explanation any help would be appreciated. greetings,3.3KViews0likes3Comments