Some not so different opinion: http://joachimtuchel.wordpress.com/2011/09/15/sunit-and-shouldshouldnt-vs-assertdeny/
2014-05-01 0:52 GMT+02:00 Nicolas Cellier < nicolas.cellier.aka.n...@gmail.com>: > Hi, > I see many usage of #should: in SciSmalltalk tests that could simply be > turned into #assert: or eventually #assert:equals: > Why wanting to use a block? > Other than #should:raise: and #shouldnt:raise:, I don't really see the > point of #should: alone anyway... > IMO should: should be deprecated, less is more. > I'm possibly the author of several of these #should: sends, so don't take > it personnally ;) > > P.S. or is it easier to restart the block in the Debugger? > I cross post to pharo-dev because it's a generic question, and there are a > few #should: sends in Pharo-3.0 too. > > -- > You received this message because you are subscribed to the Google Groups > "SciSmalltalk" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to scismalltalk+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. >