This is the mail archive of the
mailing list for the Mauve project.
Re: [Q] Number of unit tests in Mauve and of assertions in Classpath?
- From: Markus Gälli <markus dot gaelli at iam dot unibe dot ch>
- To: "PureNative Software" <info at pure-native dot com>
- Cc: "Sascha Brawer" <brawer at dandelis dot ch>,"Stephen Crawley" <crawley at dstc dot edu dot au>,<mauve-discuss at sources dot redhat dot com>
- Date: Mon, 15 Mar 2004 14:21:47 +0100
- Subject: Re: [Q] Number of unit tests in Mauve and of assertions in Classpath?
Regarding your question:Thanks for that info.
- Do you know any (as responsive :-) java open source community with
some big project and which
uses both, JDK 1.4 (thus theoretically assertions) and unit tests?
Although not a free (as in GNU) software project, NewJ Library for
independent 100% native implementation of the core Java API, uses both
tests and assertions. The test cases are our C++ version of Mauve,
make use of the gnu::testlet::Testlet and the rest of the testing
just like the Java version. The assertions are actually built right
Core J2 Library implementation, which may be compiled in or out for
release builds. As you might expect, the use of both unit tests (like
and assertions find more coding or logic errors than either one alone.
Furthermore, unit tests and assertions serve slightly different
are applicable to slightly different circumstances.
Maybe I am asking for too much here, but I would be very curious to
- #lines of code(NewJ Library),
- #assertions(NewJ Library),
- #unit tests and
- #lines of code(unit tests)
-#coverage of the unit tests
-#assertions not executed by any unit test
- over several versions?
So if you happen to be able to answer only some of this questions, this
would be great.