|
From: Luke B. <lb...@gm...> - 2005-01-08 08:20:43
|
> What about defining an interface Comparable that > has a method equals() in it? If you want to define your own definition > of equals(), you simply implement Comparable. > assertEquals should then check if the object is an instance of > Comparable, and if so, call equals(). Else it could take your approach. This sounds better to me too... > Anyway, I would like it a lot if assertEquals() could at least make a > message using the toString() methods of both objects instead of an empty > message when the test fails... I also would agree with that. Bert, how would you feel about pulling down the latest source from CVS and sending me these enhancements? I'd be glad to walk you through the CVS connection. Thanks, Luke Bayes www.asunit.com |