Forum Discussion
shankar_r
7 years agoCommunity 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
- mpolamuri7 years agoOccasional Contributor
HI Sankar
Please provide me steps to kill the Testcomplete in build steps for jenkins
- shankar_r7 years agoCommunity 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 "---------------"
- Walter216 years agoOccasional Visitor
shankar_r wrote:
I use cygwin64 in-order to execute command lines myfirstpremiercard
#!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 "---------------"
I do automated testing because there's only so much a human being can do and remain healthy. Sleep is a requirement. So, while people sleep, automation that I create does what I've described above in order to make sure that nothing gets past the final defense of the testing group.
Related Content
- 8 years ago
- 4 years ago