At 04:24 AM 12/4/2004, Andy McBride wrote:
Ok. The current frenzy around the 1.3 alpha release is great to see. I would love
to help increase the quality of the release in any way I can. I was hoping to find some time to start increasing the unit test coverage and javadoc along with testing the new functionality.
Apart from the new stuff in HISTORY.txt can you suggest any other areas in need of attention or more
unit testing?
If can't think of any really easy unit test. However, if you are not put of by a little challenge, checking for correct release of resources (by log4j) in case of web-application recycling would really be useful.
In other words, you'd to implement test cases verifying that log4j behaves properly within the target environment, say a Servlet Container such as Tomcat or Jetty. I believe this kind of testing is called integration testing.
There are two major branches to these tests, one using a log4j.jar file per web-app and the other using a single log4j.jar in conjunction with JNDIContextSelector. The latter requires JNDI support from the Container.
I started by looking at Jetty with JNDI support. The last time I looked this meant 'org.mortbay.jetty.plus.jar'. If you can manage to embed Tomcat (instead of Jetty) into the test environment that would be even better. (I made no attempts at embedding Tomcat.)
In any case, even the simplest test cases would be much better than what we have currently.
Interested?
Regards
Andy
-- Ceki G�lc�
The complete log4j manual: http://qos.ch/log4j/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
