David Röthlisberger wrote: > >> Can you check and see if it was in your code or a mistake we did? > > ah, I see what happened. > We had Kerala loaded when we committed this SUnit version, but Kerala > overrides method in SUnit such as TestResult>>runCase:, so those > methods didn't get committed. Very bad. Not bad, typical, and you get used to it winding you up if you are an MC1.0 user. So you have to adopt a strategy for maintaining each package, such as maintainng an image specifically for each package that you may have overrides in.
So that is what MC1.5 was written for, to fix this bug! But people have failed to see the need for it. Because many of you folks are package writers, rather than package users/tweakers you don't find this problem an issue. But if the package writer will not take on board requests for modifications what can you do. > I committed a new version to Pharo: SUnit-DavidRoethlisberger.42 in > which I also merged changes of stephane_ducassse.denker.41. > Let me know if you need anything else to make SUnit work. > > David the only reason you would need to override runCase: is if your SUnit doesnt include runCaseWith: aBlock as a specific place intended as a hook for test cases to wrap all tests in contexts/exception handlers. (e.g. WACurrentSession) SUnit in www.squeaksource.com/Testing includes runCaseWith: Keith _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
