|
From: | Robert Schuster |
Subject: | Re: automated mauve reports |
Date: | Mon, 19 Jul 2004 16:32:06 +0200 |
User-agent: | Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.6) Gecko/20040521 |
Hi list, tell me if I am wrong but in gnu.testlet.java.lang.Byte lines like this occur:
Isn't that (and many others) a failed test? cu Robert C. Brian Jones wrote: On Sun, 2004-07-18 at 12:32, Roman Kennke wrote:Am So, den 18.07.2004 schrieb Mark Wielaard um 16:36:Hi Roman, On Sun, 2004-07-18 at 00:23, Roman Kennke wrote:http://ontographics.com/classpath/report-index.html I still have to improve the script. When it is perfect, I will make a cron job out of it, which will fetch the current cvs of mauve and classpath and generate these reports on a nightly basis.Wow! Very useful! Would it be hard to adapt your script so it reports the number of passes/fails for each level? e.g something like: dir PASS FAIL awt 603 123 beans 78 8 io 120 67Yes, that should be no problem. I will modifiy the script, so that it generates the HTML on the fly, which enables additional options, like filtering FAIL/PASS and maybe some more.BTW. The original japhar had a mauve parsing script which is now also used by kaffe: http://www.kaffe.org/cgi-bin/viewcvs.cgi/*checkout*/kaffe/developers/mauve-html-gen.pl?rev=HEADWhy is this script not in action? /RomanYou may find something useful from these scripts as well, see http://www.haphazard.org/~cbj/classpath/automauve-1.0.tar.gz. I like how what you've done is starting towards that consolidated japi/mauve view I mentioned a couple of weeks ago. Brian |
[Prev in Thread] | Current Thread | [Next in Thread] |