This is the mail archive of the
mauve-discuss@sources.redhat.com
mailing list for the Mauve project.
Re: 600+ BigDecimal tests
- From: Mark Wielaard <mark at klomp dot org>
- To: Anthony Green <green at redhat dot com>
- Cc: mauve-discuss at sources dot redhat dot com
- Date: 17 Jan 2003 20:26:39 +0100
- Subject: Re: 600+ BigDecimal tests
- Organization:
- References: <1040597992.16986.54.camel@escape> <1041557727.20966.163.camel@elsschot>
Hi Anthony,
On Fri, 2003-01-03 at 02:35, Mark Wielaard wrote:
> On Sun, 2002-12-22 at 23:59, Anthony Green wrote:
> > I've just committed the following change...
> >
> > 2002-12-22 Anthony Green <green@redhat.com>
> >
> > * gnu/testlet/java/math/BigDecimal/DiagBigDecimal.java: New file.
> >
> > It's over 100k, so I'm not going to post it as a patch.
> >
> > It contains a large number of BigDecimal test cases. I generated it
> > by hacking on DiagBigDecimal.java from IBM's ICU project.
>
> I have been removing inner classes from the test cases since libgcj uses
> Mauve in a way that cannot handle those. Normally that is easy (just use
> the test class itself instead of creating a new inner class). But in the
> case of DiagBigDecimal I had to make a bit more changes. The changes
> mostly just remove the old test framework that IBM was using.
>
> * gnu/testlet/java/math/BigDecimal/DiagBigDecimal.java (diagrun):
> Return void.
> (DiagException): Remove and use RuntimeException if necessary.
> (summary): Removed.
> (Test): Removed.
>
> Would it be OK to commit this?
>
> If you have a way to track changes from the original test could you send
> me the script you are using then I can hack that.
Could you take a look at the above and tell me if it would be OK to
checkin this change?
BTW. I currently get the following failures with gcj. Are those expected
(bugs in Classpath/gcj?). I get the same failures with Kissme. :
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: div377 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: div203 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: div204 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: mul038 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: has001 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: lov007 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: lov107 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: mpl005 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: mpl006 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: mpl007 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: mpr005 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: mpr006 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: mpr007 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: ssc005 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: ssc006 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: ssc100 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: ssc101 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: ssc102 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: val008 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: val013 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: val100 (number 1)
Couldn't cross check against kaffe since that gives:
FAIL: uncaught exception loading
gnu.testlet.java.math.BigDecimal.DiagBigDecimaljava.lang.ExceptionInInitializerError: [exception was kaffe.util.NotImplemented]
Thanks,
Mark