"Pure" TDD (or, BDD as it's reincarnation) makes tests a documentation automatically. Unfortunately, it's not easy to find TDD examples in Smalltalk (nearly all, not just Pharo) code. Not to say, this approach would resolve a lot of other problems, if adopted just a bit wider⦠Just complaining :) 2011/8/31 Sean P. DeNigris <sean@clipperadams.com>
IMHO, the biggest room for improvement is with Tests. What I loved about BDD coming from Ruby is that it forces you to write tests from the perspective of a user of the API. Often in Squeak/Pharo, I go to the tests and still have no idea how to use the classes because the tests focus on implementation details.
-- View this message in context: http://forum.world.st/The-Keys-to-the-Kingdom-tp3780556p3780712.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
-- Dennis Schetinin