From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17537 invoked by alias); 10 Mar 2005 16:07:43 -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 16962 invoked from network); 10 Mar 2005 16:07:29 -0000 Received: from unknown (HELO mail1.ewetel.de) (212.6.122.12) by sourceware.org with SMTP; 10 Mar 2005 16:07:29 -0000 Received: from majestix.konqueror.de (dyndsl-080-228-196-089.ewe-ip-backbone.de [80.228.196.89]) by mail1.ewetel.de (8.12.1/8.12.9) with ESMTP id j2AG7Pph010923; Thu, 10 Mar 2005 17:07:26 +0100 (MET) Received: from [192.168.1.10] (helo=papacharly.konqueror.de) by majestix.konqueror.de with smtp (Exim 4.44) id 1D9QCi-00049Q-1c; Thu, 10 Mar 2005 17:08:04 +0100 Received: by papacharly.konqueror.de (sSMTP sendmail emulation); Thu, 10 Mar 2005 17:05:10 +0100 Date: Thu, 10 Mar 2005 16:07:00 -0000 From: Michael Koch To: Meskauskas Audrius Cc: mauve-discuss@sources.redhat.com Subject: Re: A place for the Classpath specific tests Message-ID: <20050310160510.GI4737@papacharly.konqueror.de> References: <000701c5257c$0afc0c70$2101a8c0@computername> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000701c5257c$0afc0c70$2101a8c0@computername> User-Agent: mutt-ng/1.5.8-r150i (Debian) X-CheckCompat: OK X-SW-Source: 2005-q1/txt/msg00037.txt.bz2 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. Michael -- Java Trap: http://www.gnu.org/philosophy/java-trap.html