RE: Full compile, almost ready to run

Okay, that is impressive.  I got the test suite to build only 5 hours ago and ran out of steam before I trying to run it, and somebody replicates the build and runs it first.

Using multiple asserts (as suggested) is definitely much preferred over building expected and results lists and then doing an assertEquals.  With the multiple asserts, you will know which part failed.
If there isn't some kind of iterative loop, then you shouldn't be using assertEquals(List,List) or assertEquals(Collection,Collection).  However, when you do have an iterative loop, then those
constructs are extremely useful.  The pattern was inherited from the early NIST work which could only have one assert per test.

While repairing some other issues, I did take the liberty of rewriting a few other places where assertEquals(Collection/List, Collection/List) were used, but I did not try to fix any others that
compiled successfully.

I had noticed the discontinuation of Avalon testlet development (announced 1 Aug, I believe) right after completing the Avalon testlet adapter.  Definitely, JUnit was primary emphasis.  I had done the
Avalon Testlet since the Batik project were interested by the DOM test suite, but couldn't run Junit as part of their build process.  I assume that Apache and JUnit have found some way to work with
each others licenses.  I apparently bungled the JUnit target when I added the Avalon code.

Received on Monday, 20 August 2001 09:20:31 UTC