On 26-11-10 14:27, Patricia Shanahan wrote:
Sim IJskes - QCG wrote:
Suppose we have a good kill mechanism for all the testing slave VMs,
would there be any harm in activating this kill mechanism during
teardown? So no orderly teardown, but a brute kill.
I see only two issues:
1. Making the brute kill work all the time, including reclaiming *all*
resources.
A self initiated System.exit(0) or better, Runtime.halt(0) should be
enough. I would like to check the keep-alive port mechanism, and if it
does not work, activate it.
2. Ensuring that the River features that are used during the current
teardown are tested in some other way.
But only if the teardown is already part of the testresult. Is it?
Gr. Sim
--
QCG, Software voor het MKB, 071-5890970, http://www.qcg.nl
Quality Consultancy Group b.v., Leiderdorp, Kvk Den Haag: 28088397
