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: "PureNative Software" <info at pure-native dot com>
- To: Markus Gälli <markus dot gaelli at iam dot unibe dot ch>
- 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 22:07:22 -0500
- Subject: Re: [Q] Number of unit tests in Mauve and of assertions in Classpath?
- References: <B634356B-7683-11D8-90B9-000A958C4F3C@iam.unibe.ch>
Here are some stats for you.
NewJ Library is made up of the Pie Library, which is the foundation layer
for automated object management and approximating Java language features in
C++, and the Core J2 Library, which implements the core Java APIs like lang,
io, util, etc. in C++. Both libraries combined consist of the following:
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 Mauve
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 so,
that would be very difficult to provide to you.
(b) By "over several versions" of the Java API or specification. If so, NewJ
Library supports 1.2 and some 1.4 features like assertions. Everything is in
the same code base, compile-in or compile-out at build time, so it's all the
For more detailed information, download the trial version from
pure-native.com, read the NewJ Developer's Guide (they're quite detailed and
only around 50 pages), and peruse the included header files and samples.
Hope this helps.
----- Original Message -----
From: "Markus Gälli" <email@example.com>
To: "PureNative Software" <firstname.lastname@example.org>
Cc: "Sascha Brawer" <email@example.com>; "Stephen Crawley"
Sent: Monday, March 15, 2004 8:21 AM
Subject: Re: [Q] Number of unit tests in Mauve and of assertions in
> Hi Vargas,
> > Regarding your question:
> >>>> - 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
> > C++, an
> > independent 100% native implementation of the core Java API, uses both
> > unit
> > tests and assertions. The test cases are our C++ version of Mauve,
> > which
> > make use of the gnu::testlet::Testlet and the rest of the testing
> > framework
> > just like the Java version. The assertions are actually built right
> > into the
> > Core J2 Library implementation, which may be compiled in or out for
> > debug or
> > release builds. As you might expect, the use of both unit tests (like
> > Mauve)
> > and assertions find more coding or logic errors than either one alone.
> > Furthermore, unit tests and assertions serve slightly different
> > purposes and
> > are applicable to slightly different circumstances.
> Thanks for that info.
> Maybe I am asking for too much here, but I would be very curious to
> know the
> - #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.