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: "Byron Vargas" <byron dot vargas at worldpost 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: Tue, 16 Mar 2004 13:55:39 +0100
- Subject: Re: [Q] Number of unit tests in Mauve and of assertions in Classpath?
Here are some stats for you.
Thanks a lot for that detailed description. This is really of some use
for me, I just
could not include it in my paper as the submission deadline was one
I'd be curious, if you could also provide me with a version name of
where this data holds.
As I was not successful to download Mauve (I tried the ftp version,
but the server seems to be down, then my OS-X stopped without throwing
I would also like to know how many assertions are called inside the
maybe you or someone else can answer this question too? Then I stop
Thanks again, this can be of some great value in one of the next papers
I want to write,
I'll submit the old one as soon as I get it accepted somewhere.
NewJ Library is made up of the Pie Library, which is the foundation
for automated object management and approximating Java language
C++, and the Core J2 Library, which implements the core Java APIs like
io, util, etc. in C++. Both libraries combined consist of the
Total lines: 100757
Comment lines: 22542 (22.372638702% of total)
Source code lines: 53245 (52.844963074% of total)
Blank lines: 24970 (24.782396317% of total)
Number of assertions in Pie Library: 43
Number of assertions in Core J2 Library (java.* packages): 441
Number of assertions in Core J2 Library (private packages): 221
Additionally, the code base includes debug-only sections which take
advantage of conditional compilation inherent in C++.
Number of units tests, coverage, lines: Same as the Java version of
for the packages and classes we support.
"Assertions not executed by any unit test": We have no quantitative
information on that.
By "over several versions," what should I understand that to mean?
(a) By "over several versions" of NewJ Library, like 0.1, 0.2, 0.3. If
that would be very difficult to provide to you.
(b) By "over several versions" of the Java API or specification. If
Library supports 1.2 and some 1.4 features like assertions. Everything
the same code base, compile-in or compile-out at build time, so it's
For more detailed information, download the trial version from
pure-native.com, read the NewJ Developer's Guide (they're quite
only around 50 pages), and peruse the included header files and
Hope this helps.
----- Original Message -----
From: "Markus Gälli" <firstname.lastname@example.org>
To: "PureNative Software" <email@example.com>
Cc: "Sascha Brawer" <firstname.lastname@example.org>; "Stephen Crawley"
Sent: Monday, March 15, 2004 8:21 AM
Subject: Re: [Q] Number of unit tests in Mauve and of assertions in
Regarding your question:Thanks for that info.
- Do you know any (as responsive :-) java open source community
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
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
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,
would be great.