Similarly with Commons IO, there is a single test case [1] for ClassLoaderObjectInputStream which could use the approach proposed by Simon.
[1] http://svn.apache.org/repos/asf/jakarta/commons/proper/io/trunk/src/test /org/apache/commons/io/input/ClassLoaderObjectInputStreamTest.java ----- Tim O'Brien [EMAIL PROTECTED] (847) 863-7045 > -----Original Message----- > From: Torsten Curdt [mailto:[EMAIL PROTECTED] > Sent: Wednesday, June 29, 2005 4:10 PM > To: Jakarta Commons Developers List > Subject: Re: [logging] unit test refactoring > > > I find the general approach quite brilliant. It might be the right > > answer to the bigger problem of testing class loader > related issues with > > Junit instead of through a static main method. However, the > approach has > > the disadvantage of displacing some of the test logic into junit. Of > > course, the displacement in logic is unavoidable by construction. > > > > You have either created a new testing idiom to be followed > by many java > > developers, > > You already got me interested - jci and javaflow also need > to test classloaders ...and frankly - the current approach > just sucks ;) > > cheers > -- > Torsten > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
