From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10186 invoked by alias); 17 Jul 2002 09:32:33 -0000 Mailing-List: contact mauve-discuss-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: mauve-discuss-owner@sources.redhat.com Received: (qmail 10156 invoked from network); 17 Jul 2002 09:32:31 -0000 Received: from unknown (HELO web10002.mail.yahoo.com) (216.136.130.38) by sources.redhat.com with SMTP; 17 Jul 2002 09:32:31 -0000 Message-ID: <20020717093230.34304.qmail@web10002.mail.yahoo.com> Received: from [149.225.94.191] by web10002.mail.yahoo.com via HTTP; Wed, 17 Jul 2002 02:32:30 PDT Date: Wed, 17 Jul 2002 02:32:00 -0000 From: Dalibor Topic Subject: Re: [Kissme-general] Re: Should I or not submit changes? To: Brian Jones , Stephen Crawley Cc: John Leuner , Alex Lau , kissme-general@lists.sourceforge.net, Mark Wielaard , mauve-discuss@sources.redhat.com In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2002-q3/txt/msg00003.txt.bz2 --- Brian Jones wrote: > Stephen Crawley 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. http://sources.redhat.com/ml/mauve-discuss/2002-q2/msg00037.html It has also came up on the classpath X mailing list: http://mail.gnu.org/pipermail/classpathx-discuss/2001-December/000095.html There is a nice discussion on pros and cons of junit on the xml-dev list: http://lists.xml.org/archives/xml-dev/200107/msg00131.html 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 libraries. ;) 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 contributors. best regards, dalibor topic __________________________________________________ Do You Yahoo!? Yahoo! Autos - Get free new car price quotes http://autos.yahoo.com