From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10891 invoked by alias); 10 Mar 2005 14:19:10 -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 10258 invoked from network); 10 Mar 2005 14:18:34 -0000 Received: from unknown (HELO mail17.bluewin.ch) (195.186.18.64) by sourceware.org with SMTP; 10 Mar 2005 14:18:34 -0000 Received: from computername (83.79.176.34) by mail17.bluewin.ch (Bluewin AG 7.0.035) id 42011C3800372026; Thu, 10 Mar 2005 14:18:33 +0000 Message-ID: <000701c5257c$0afc0c70$2101a8c0@computername> Reply-To: "Meskauskas Audrius" From: "Meskauskas Audrius" To: Cc: "Michael Koch" Subject: A place for the Classpath specific tests Date: Thu, 10 Mar 2005 14:19:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-SW-Source: 2005-q1/txt/msg00036.txt.bz2 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. Regards Audrius