From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7254 invoked by alias); 10 Mar 2005 16:21:20 -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 7033 invoked from network); 10 Mar 2005 16:21:11 -0000 Received: from unknown (HELO francois.mpi-sb.mpg.de) (139.19.1.2) by sourceware.org with SMTP; 10 Mar 2005 16:21:11 -0000 Received: from amavis by francois.mpi-sb.mpg.de with scanned-ok (Exim 3.36 #1 (Debian)) id 1D9QPP-0003nV-00 for ; Thu, 10 Mar 2005 17:21:11 +0100 Received: from maildist ([139.19.90.238] helo=mpi-sb.mpg.de) by francois.mpi-sb.mpg.de with esmtp (Exim 3.36 #1 (Debian)) id 1D9QPM-0003n1-00; Thu, 10 Mar 2005 17:21:08 +0100 Received: from [139.19.20.94] (topic@mpiat2305 [139.19.20.94]) by mpi-sb.mpg.de (8.12.9+Sun/8.12.9) with ESMTP id j2AGL8Nw011865; Thu, 10 Mar 2005 17:21:08 +0100 (MET) Message-ID: <423073F3.6000102@kaffe.org> Date: Thu, 10 Mar 2005 16:21:00 -0000 From: Dalibor Topic User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20050105 Debian/1.7.5-1 MIME-Version: 1.0 To: Michael Koch CC: Meskauskas Audrius , mauve-discuss@sources.redhat.com Subject: Re: A place for the Classpath specific tests References: <000701c5257c$0afc0c70$2101a8c0@computername> <20050310160510.GI4737@papacharly.konqueror.de> In-Reply-To: <20050310160510.GI4737@papacharly.konqueror.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2005-q1/txt/msg00038.txt.bz2 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