From: Dalibor Topic <robilad@kaffe.org>
To: Michael Koch <konqueror@gmx.de>
Cc: Meskauskas Audrius <audriusa@bluewin.ch>,
mauve-discuss@sources.redhat.com
Subject: Re: A place for the Classpath specific tests
Date: Thu, 10 Mar 2005 16:21:00 -0000 [thread overview]
Message-ID: <423073F3.6000102@kaffe.org> (raw)
In-Reply-To: <20050310160510.GI4737@papacharly.konqueror.de>
Michael Koch wrote:
> On Thu, Mar 10, 2005 at 03:18:33PM +0100, Meskauskas Audrius wrote:
>
>>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.
>
>
> We should really put the tests in muave. Into a specific CVS module if
> needed/wanted. We have already classpath specific tests in Mauve. If we
> consider an extra module is need then we should move them into it.
I'd say mauve, too. If a test is Classpath specific, then it can be
tagged as such.
cheers,
dalibor topic
next prev parent reply other threads:[~2005-03-10 16:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-10 14:19 Meskauskas Audrius
2005-03-10 16:07 ` Michael Koch
2005-03-10 16:21 ` Dalibor Topic [this message]
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=423073F3.6000102@kaffe.org \
--to=robilad@kaffe.org \
--cc=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).