From: "Meskauskas Audrius" <audriusa@bluewin.ch>
To: <mauve-discuss@sources.redhat.com>
Cc: "Michael Koch" <konqueror@gmx.de>
Subject: A place for the Classpath specific tests
Date: Thu, 10 Mar 2005 14:19:00 -0000 [thread overview]
Message-ID: <000701c5257c$0afc0c70$2101a8c0@computername> (raw)
For a project as large as Classpath, it would be good to
have a tests for all important classes. Apart the standard
java.* and javax.* , this also includes the Classpath
specific classes from gnu.* namespace. In some
packages this namespace contains many classes,
having hundreds lines of the working code.
Even it they run ok today, staying without tests leaves a gap for
the future regression bugs.
It is not immediatly clear if such tests can be contributed to
Mauve. With such tests the Mauve would not compile
without the newest version of Classpath.
Classpath has its own small test suite. While not very popular
and requiring to write all tests in the form of the executable
classes, it could be treated as an alternative.
Before committing Classpath specific tests to Mauve, I would
like to discuss this question in the list.
Regards
Audrius
next reply other threads:[~2005-03-10 14:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-10 14:19 Meskauskas Audrius [this message]
2005-03-10 16:07 ` Michael Koch
2005-03-10 16:21 ` Dalibor Topic
2005-03-12 19:24 ` Tom Tromey
2005-03-15 17:37 ` Mark Wielaard
2005-03-15 17:55 ` Tom Tromey
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='000701c5257c$0afc0c70$2101a8c0@computername' \
--to=audriusa@bluewin.ch \
--cc=konqueror@gmx.de \
--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).