On Tue, 26 Feb 2002, Morgan Delagrange wrote: > Actually, I think the names below, which I drew from the current Collections > test classes, are slightly misleading. I think there should be a > "TestObject" test case, which tests the methods of Object. For most other > tasks, we probably want a library of custom asserts, rather than actual test > cases. That seems to be the only reasonable course, since interfaces can be > combined in any number of ways.
I've been thinking about the "library of custom asserts" a bit as well, but have yet to reach a design/impl that I'm happy with. My primary motivation was primarily for being able to use the same tests for testing the entrySet(), keySet(), and values() that are used for testing Maps, and Collections. This is almost the same thing as you imply about being able to test interfaces. michael -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
