This is the mail archive of the
mailing list for the Mauve project.
Re: [Kissme-general] Re: Should I or not submit changes?
- From: Dalibor Topic <robilad at yahoo dot com>
- To: Brian Jones <cbj at gnu dot org>, Stephen Crawley <crawley at dstc dot edu dot au>
- Cc: John Leuner <jewel at pixie dot co dot za>, Alex Lau <alex at dentonlive dot com>, kissme-general at lists dot sourceforge dot net, Mark Wielaard <mark at klomp dot org>, mauve-discuss at sources dot redhat dot com
- Date: Wed, 17 Jul 2002 02:32:30 -0700 (PDT)
- Subject: Re: [Kissme-general] Re: Should I or not submit changes?
--- Brian Jones <firstname.lastname@example.org> wrote:
> Stephen Crawley <email@example.com> writes:
> Yes, it really sucks to try to use Mauve in certain
> ways. If anyone
> has loads of time it would probably be more
> interesting to develop
> junit based tests from the classpath source as a
> start and gradual
> port of the Mauve tests to what is usually a more
> familiar test
> framework to developers at large.
Junit has been lightly discussed on mauve this spring.
It has also came up on the classpath X mailing list:
There is a nice discussion on pros and cons of junit
on the xml-dev list:
Porting tests over to Junit might not be too exciting,
though. I believe that (if the mauve hackers decide to
allow junit tests) it would be a better option to have
both frameworks in parallel for a while. As junit
relies on reflection, it wouldn't make much sense to
run it on an implementation with broken reflection
The major point junit has for it, in my opinion, is
the amount of documentation surrounding it: books,
tutorials etc. It seems to be easy to find answers.
That could lower the entry barrier for fresh mauve
Do You Yahoo!?
Yahoo! Autos - Get free new car price quotes