Great post... a lot to think about :) Adrian Kuhn wrote
Classes and methods are not the best model to structure tests. Alas in Smalltalk it's all we can work with.... we cannot break free from classes and methods (imposed by the Smalltalk IDE rather than the language) so its what we must work with.
I consider classes and methods to be the assembler of specifications (I prefer to "testing"). Because we have our amazing IDE, with Smalltalk turtles all the way down, all there is to do is create a GUI that works the way our minds do. Just like Spec will eventually have a painter covering the raw spec methods, so too can we have a Specification Painter. I started work on this several times, but there was so much cleaning to do in Pharo... But with all the progress made for 2.0, I feel that we are getting closer and closer and have been wanting to resume my work on that this week. It seems that a Morphic overhaul is the only thing left to make that easier, and at least a new text model (one of the more infuriating parts of Morphic) is already underway. Cheers, Sean -- View this message in context: http://forum.world.st/Re-Phexample-should-methods-tp4670589p4670629.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.