Meaningfull tests for every class are a good goal, and the test server will make them much more meaningful. OTOH, I don't think checking for a class comment is a good use for a test, it's too wasteful.
What I think we should do to improve these things is use SLint rules, and have the test server run those too (in some future release, it's not important to do this right now - most important is to start running tests regularly).
Daniel
Marcus Denker marcus@ira.uka.de wrote:
There's actually a test in the Tests-package for that: I've done a Abstract testing-class called "ClassTestCase". If you inherit from this one instead of TestCase (and name the test "<name of the class>Test", you get an error if the class-comment is empty.
(and you get 3 more tests: testNew, testUnCategorizedMethods, testRecompileAll)
There are not yet tests for every class in the system, but as soon as the testserver is running, I'l add more.
Marcus
-- Marcus Denker marcus@ira.uka.de -- Squeak! http://squeak.de
Squeakfoundation mailing list Squeakfoundation@lists.squeakfoundation.org http://lists.squeakfoundation.org/listinfo/squeakfoundation
squeakfoundation@lists.squeakfoundation.org