What Hernán did is here: http://www.squeaksource.com/TDDFacilities.html
That was for Pharo 1.0. For those that want to help in this subject I think the first step could be to load such package in a PharoCore1.1 and fix it in case it doesn't work. Then, it can be integrated as part of PharoCore. Although it may be cool to have a preference to enable or disable all this changes (more TDD oriented), as we are not doing TDD all the time and sometimes we want the normal behavior. Once we have that, we can start improving. For example, I would love also what Guille said: key bindings for the debugger. I would LOVE to have a Pharo less mouse oriented (I don't care who invented the mouse, I rather the keyboard). So..open a bug ticket and start to play. Cheers Mariano 2010/6/3 Denis Kudriashov <[email protected]> > Hello, No I dont. Who is it? > > 2010/6/3 Stéphane Ducasse <[email protected]> > > do you happen to know tim mckinnon? >> >> Stef >> On Jun 3, 2010, at 12:13 AM, Denis Kudriashov wrote: >> >> > I use Mockery - my implementation SSpec idies. It is realy more >> powerfull, transparency and flexibility. >> > >> > With Mockery you dont need any special base classes for TestCases or >> mocks factory variables in code. You just use mocks where you want by Block >> creation scenarios: >> > >> > [:mock | >> > [sut doWith: mock] should lenient satisfy: [mock someMessage >> willReturn: #result] >> > ] runScenario. >> > >> > State specs like "5 should be an instance of: Integer" can be easely >> added by pragmas. >> > >> > And Its work in Pharo 1.0. >> > >> > Of course, It's needs more good stuff. But now I dont have enough time. >> > http://www.squeaksource.com/Mocketry.html >> > >> > 2010/6/3 Sean P. DeNigris <[email protected]> >> > >> > >> > Stéphane Ducasse wrote: >> > > >> > > Imagine that we would like to sell pharo (+ seaside) as THE agile >> platform >> > > for doing TDD. >> > > What would be the changes that we could do support it. >> > > >> > >> > Coming from Ruby, it seemed like BDD was taking over the world, and was >> the >> > next step in TDD evolution, but I found few mentions of it in the Squeak >> > world. For my own projects, I use SSpec (which I have been fixing as I >> go >> > along). I only use "tests" with SUnit assertions for community >> projects, as >> > not to confuse or add additional dependencies. >> > >> > I think that core BDD support would be necessary to woo developers here, >> > especially from Ruby, where all the passion and conversation is around >> BDD. >> > >> > Sean >> > -- >> > View this message in context: >> http://forum.world.st/About-TDD-and-Pharo-tp2240686p2240877.html >> > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> > >> > _______________________________________________ >> > Pharo-project mailing list >> > [email protected] >> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > >> > _______________________________________________ >> > Pharo-project mailing list >> > [email protected] >> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> [email protected] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >
_______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
