From: "Markus Gälli" <markus.gaelli@iam.unibe.ch>
To: "PureNative Software" <info@pure-native.com>
Cc: "Sascha Brawer" <brawer@dandelis.ch>,
"Stephen Crawley" <crawley@dstc.edu.au>,
<mauve-discuss@sources.redhat.com>
Subject: Re: [Q] Number of unit tests in Mauve and of assertions in Classpath?
Date: Mon, 15 Mar 2004 13:21:00 -0000 [thread overview]
Message-ID: <B634356B-7683-11D8-90B9-000A958C4F3C@iam.unibe.ch> (raw)
In-Reply-To: <000c01c40a8c$0a7697e0$9865fea9@yourviu5vcdub5>
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.
Cheers,
Markus
next prev parent reply other threads:[~2004-03-15 13:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-11 6:28 Markus Gälli
2004-03-11 6:49 ` Stephen Crawley
2004-03-11 8:19 ` Markus Gälli
2004-03-11 9:34 ` Sascha Brawer
2004-03-11 10:51 ` Markus Gälli
2004-03-15 12:46 ` PureNative Software
2004-03-15 13:21 ` Markus Gälli [this message]
2004-03-16 3:04 ` Byron Vargas
2004-03-16 12:55 ` Markus Gälli
2004-03-16 17:15 ` PureNative Software
2004-03-16 3:04 ` PureNative Software
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=B634356B-7683-11D8-90B9-000A958C4F3C@iam.unibe.ch \
--to=markus.gaelli@iam.unibe.ch \
--cc=brawer@dandelis.ch \
--cc=crawley@dstc.edu.au \
--cc=info@pure-native.com \
--cc=mauve-discuss@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).