Ask a Question

unable close test complete after Jenkins job

mpolamuri
Occasional Contributor

unable close test complete after Jenkins job

When i am running Jenkins job after completing execution tests unable close test complete. it take more than 1 hr to close.

I am using Test complete version 12

5 REPLIES 5
tristaanogre
Community Hero

Re: unable close test complete after Jenkins job

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.


Robert Martin
[Hall of Fame]
Please consider giving a Kudo if I write good stuff
----

Why automate?  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.
I love good food, good books, good friends, and good fun.

Mysterious Gremlin Master
Vegas Thrill Rider
Extensions available
shankar_r
Community Hero

Re: unable close test complete after Jenkins job

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


Thanks
Shankar R

LinkedIn | CG-VAK Software | Bitbucket | shankarr.75@gmail.com

“You must expect great things from you, before you can do them”

Extension Available

mpolamuri
Occasional Contributor

Re: unable close test complete after Jenkins job

HI Sankar

 

Please provide me steps to kill the Testcomplete in build steps for jenkins

shankar_r
Community Hero

Re: unable close test complete after Jenkins job

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 "---------------"

Thanks
Shankar R

LinkedIn | CG-VAK Software | Bitbucket | shankarr.75@gmail.com

“You must expect great things from you, before you can do them”

Extension Available

Walter21
Occasional Visitor

Re: unable close test complete after Jenkins job


@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.

cancel
Showing results for 
Search instead for 
Did you mean: