Adrian Kuhn wrote: > A first fork is available > > Gofer it > squeaksource: 'akuhn'; > package: 'SUnit'; > package: 'SUnitGUI'; > load
Is it too late to call it SUnit2, SUnit3, whatever? When I see SUnit, I expect only the "standard" SUnit (i.e. TestCase, TestSuite, test resources, and various #assert: methods). Am I the only one that has a problem with calling this new direction "SUnit", without qualifying it with some version. I see a parallel with JUnit 3 vs 4 in the Java world. JUnit4 uses annotations to indicate test cases - no "test" prefix needed. When these test cases are run against JUnit3, nothing fails (and it appears to have passed) - but the tests have not been run at all, since without the "test" prefix, they're not recognized as test cases. Maybe nothing similar will happen with the new SUnit. What happens is that people start writing test cases assuming the newer version. Then at some point there's a conflict, and you either have to re-write your old or your new test cases. Maybe it's okay to be forced to update your old test cases, but it would be good know which version of the "SUnit API" is available or required. -- Yanni Chiu _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
