classpath project and gcj

[d.frost]

Tom Tromey wrote:

> How are you testing them?

I test them against the examples from the JCL, which although not
exhaustive, make for pretty good sanity checks of the basic
functionality
and for things like fail-fast iterator behaviour. You can download them
at http://java.sun.com/docs/books/chanlee/supplement/ . I tend to also
write ad-hoc extensions to these where I want to quickly test particular
functionality - not a good approach if we want to put them in mauve, I
know.

> I think we should start being more careful about doing testing.  For
> instance as we merge with Classpath it would be good if we had Mauve
> tests for classes we are merging.  I realize that doing thorough
> testing is really hard.  However, even minimal tests of classes would
> be better than what we do now.  Also, maybe this would encourage us to
> write regression tests as we fix bugs -- another practice I'd like to
> see us adopt.

Agreed. I'd like to see mauve support simple output-comparison Dejagnu
style test cases like the existing libjava/testsuite stuff. That would
make it easier to write and run simple tests.

regards

  [ bryce ]