Sure, there are objects: it's Smalltalk, methods are obects too :) That's really correct: SUnit is the simplest thing that (still) works. But is it still enough? Isn't it a time to make more steps and improve?
I just mean it would be great to have test as distinct object that I can explore, add certain behavior and properties to, relate to other objects in system (other tests, test suites, groups and more), open in specific tools (to be yet created), log all runs and results… and associate with frameworks that it should be run within… In general, to create a full-fledged and easy-to-use environment for TDD and controlling all the development steps with tests, use them as documentation, etc. etc. etc. -- Best regards, Dennis Schetinin 2013/12/3 Esteban A. Maringolo <[email protected]> > 2013/12/3 Dennis Schetinin <[email protected]> > > > > I see the only correct way to build a good testing environment: tests > should be basically objects, not methods. > > They are objects. Instances of TestCase. > > But for simplicity they're implemented in a single "factory" class, > the TestCase subclass... > > > > Esteban A. Maringolo > >
