From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17423 invoked by alias); 17 Jul 2002 19:15:31 -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 17414 invoked from network); 17 Jul 2002 19:15:29 -0000 Received: from unknown (HELO mail.testingtools.com) (63.149.152.2) by sources.redhat.com with SMTP; 17 Jul 2002 19:15:29 -0000 Received: from smtp.dpcgroup.com (smtp.dpcgroup.com [63.149.152.8]) by mail.testingtools.com (8.9.3/linuxconf) with ESMTP id OAA17848; Wed, 17 Jul 2002 14:14:50 -0500 Received: from dentonlive.com (unknown [63.149.152.202]) by smtp.dpcgroup.com (Postfix) with ESMTP id 5C17072DE3; Wed, 17 Jul 2002 14:14:50 -0500 (CDT) Message-ID: <3D35BFF9.3050001@dentonlive.com> Date: Wed, 17 Jul 2002 12:15:00 -0000 From: Alex Lau User-Agent: Mozilla/5.0 (X11; U; Linux i686; zh-TW; rv:1.0.0) Gecko/20020615 Debian/1.0.0-3 X-Accept-Language: zh-hk, zh-tw, zh MIME-Version: 1.0 To: Stephen Crawley Cc: John Leuner , kissme-general@lists.sourceforge.net, mauve-discuss@sources.redhat.com Subject: Re: [Kissme-general] Re: Should I or not submit changes? References: <200207171548.g6HFmnR12190@piglet.dstc.edu.au> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-q3/txt/msg00008.txt.bz2 Stephen Crawley >Alex, > > > >>I couldn't find the mauve-kissme file ... >> >> > >It is there now. Look in the kissme CVS for useful-scripts/mauve-kissme. >Also look at the 'run-mauve-regression' rule in the latest version of the >Makefile. > >[I'm sorry this took so long. I trashed my home directory and had >to rebuild it. :-(] > > > not a problem :) I'm still playing with all the script and hope to able to find a way to make the testing and generating test and running test a lot easier then right now. I see how you use the mauve-kissme to run the full test ( regression ) but I have a different reason to use the buildtest.sh script, is isolating the range of the test. Like in the mauve-kissme, it identifly some test is no good to run. Unless who has a good understanding of mauve and kissme and classpath code like you, or else it will very hard to identifly them. For me it is not easy to sort it out. So far what I have been trying to do is take one sub directory at a time to run the test on... and that is what buildtest.sh for. I'm not trying to say my script is any good. But I really like to see some more control to generate test and running test as need ( rather then all or one ). If that some level of control is existing, please let me know. e.g. KEY file include java.io.* should only test on java.io.* classes right? ( I never get it to run the way I wanted ) Thanks Alex