On Dec 3, 2004, at 7:03 AM, Ceki G�lc� wrote:
One of the important tasks to be done before releasing 1.3, is to write unit tests which go through the whole web-app lifecycle to check that log4j releases all resources correctly. I started doing that with jetty but got sidetracked.
Anyway, I'd appreciate small and manageable test cases reproducing the problem. You are a log4j committer, have you considered submitting test cases verifying that resources are correctly handled by log4j?
Have you given any thoughts about doing coverage analysis on the tests to see how much of the code base is tested (and identify dead code)? I've used Clover (http://www.cenqua.com/clover/) on other projects and it has been fairly straightforward. The product is commercial, but will give free licenses for Open Source project developers.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
