Forum Discussion
I'd kill it with PowerShell in the batch file if you want to be certain it's no longer running.
PS C:\> Stop-Process -Name "testexecute"
Stop-Process (Microsoft.PowerShell.Management) - PowerShell | Microsoft Learn
- Hassan_Ballan3 months agoContributor
In batch file, you could use the command line "TASKKILL /IM testexecute.exe" rather than adding PoweShell, its really a matter of preference.
On command line run C:\>taskkill /? for the help
- beginTC3 months agoOccasional Contributor
I created a batch file to terminate the TestExecute to be initiated after my test is done. The batch could terminate the TestExecute, then QAComplete could receive the log. The issue is that the QAComplete will display all to be "Passed" even when the test is failed...
I think the termination using command line will somehow send back the exit code or whatever code to QAComplete to indicate the result. Since the termination command is passed, the QAComplete will always display as passed...
- JDR25003 months agoFrequent Contributor
What about killing the process before you start your tests running rather than at the end? We do something like that to make sure our application isn't running when we try to install/uninstall it. Jenkins runs the PS script before launching the TestComplete project.
- beginTC3 months agoOccasional Contributor
I mean I could do that. But starting the test is always fine for me. It is about stopping the test. We are using QAComplete to control the TestExecute to test in local computer, but the QAComplete cannot stop the TestExecute.
Related Content
- 4 years ago
Recent Discussions
- 4 hours ago