This is the mail archive of the
mailing list for the Mauve project.
Re: [Kissme-general] Re: Should I or not submit changes?
- From: Alex Lau <alex at dentonlive dot com>
- To: Stephen Crawley <crawley at dstc dot edu dot au>
- Cc: John Leuner <jewel at pixie dot co dot za>, kissme-general at lists dot sourceforge dot net, mauve-discuss at sources dot redhat dot com
- Date: Wed, 17 Jul 2002 14:05:29 -0500
- Subject: Re: [Kissme-general] Re: Should I or not submit changes?
- References: <200207171548.g6HFmnR12190@piglet.dstc.edu.au>
Alex,not a problem :) I'm still playing with all the script and hope to able
to find a
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
[I'm sorry this took so long. I trashed my home directory and had
to rebuild it. :-(]
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
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
directory at a time to run the test on... and that is what buildtest.sh
I'm not trying to say my script is any good. But I really like to see
control to generate test and running test as need ( rather then all or
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
( I never get it to run the way I wanted )