From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14437 invoked by alias); 29 Oct 2004 06:41:42 -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 14425 invoked from network); 29 Oct 2004 06:41:41 -0000 Received: from unknown (HELO johanna.resare.com) (193.14.119.138) by sourceware.org with SMTP; 29 Oct 2004 06:41:41 -0000 Received: from molly.resare.com (c-771f72d5.01-60-6c6b701.cust.bredbandsbolaget.se [213.114.31.119]) by johanna.resare.com (Postfix) with ESMTP id 19CE9D6BD0 for ; Fri, 29 Oct 2004 08:40:52 +0200 (CEST) Received: from 192.168.110.42 (marit [192.168.110.42]) by molly.resare.com (Postfix) with ESMTP id 0B2A7D2DFE for ; Fri, 29 Oct 2004 08:41:41 +0200 (CEST) Subject: future plans for mauve From: Noa Resare To: mauve-discuss@sources.redhat.com Content-Type: text/plain Date: Fri, 29 Oct 2004 06:41:00 -0000 Message-Id: <1099032100.2198.50.camel@c-241f72d5.01-60-6c6b701.cust.bredbandsbolaget.se> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-SW-Source: 2004-q4/txt/msg00035.txt.bz2 Hello While using mauve for a while now I have felt an urge to put some time into change/fix some things that I think could be done better. This will not happen right now, as I would like to see kaffe-1.1.5 out the door first and I'm going offline for a week tonight but I thought it would be a good idea to share my ideas with the list anyway, especially since David Gilbert seems to be thinking about using a mauve for testing other code than the class library. Note that these are just random thoughts, and I'm really open to suggestions. * The './configure; make tests ARGS' invocation scheme is a little odd. I'd like to have a small script perhaps called 'mauve' that took arguments --java=/path/to/java --javac=/path/to/javac. The rest of the args should be like the KEYS variable. * Changes in mauve-KEYWORD files should trigger a recalculation of which classes should be tested. * The mechanism now implemented in the choose script should be faster and written in a language more suited for the task. java perhaps? * Improved documentation. There should be a 'write a new test guide' of some sort. * Package structure. The part that could be called the 'testlet api' should live in gnu.testlet. The test runner implementation should be in gnu.mauve.runner (?) and test hierarchy perhaps in gnu.mauve.tests. * Improved progress reporting when doing the tests. /noa