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
