Forum Discussion
5 Replies
Sort By
- shankar_rCommunity Hero
And also, there are some cases where TestComplete/TestExecute might not close even after completion of job. You can add a command line build step in-order to kill the testcomplet.exe/testexecute.exe process
- mpolamuriOccasional Contributor
HI Sankar
Please provide me steps to kill the Testcomplete in build steps for jenkins
- shankar_rCommunity Hero
I use cygwin64 in-order to execute command lines
#!c:\cygwin64\bin\bash.exe --login set +x echo "Terminate TestExecute" pids=`tasklist | grep TestExecute.exe | awk '{printf ("%s ",$2)}'` echo $pids if [ "$pids" != "" ]; then for pid in $pids do echo "Terminating pid: $pid" taskkill /f /t /pid $pid done else echo "No processes found to terminate" fi echo "---------------"
- tristaanogreEsteemed Contributor
At close, TestComplete flushes the log to disk. The timing might have to do with that, depending upon how much you're writing out to your test log.