Status: Accepted Owner: da...@teleport.com New issue 3391 by da...@teleport.com: BlockClosure>>assertWithDescription: sends #logFailure: http://code.google.com/p/pharo/issues/detail?id=3391 In a PharoCore image (Pharo1.1.1 #11414 or Pharo1.2a #12271) the only sender of #assertWithDescription: is RxMatcher>>split: ... which wouldn't be that bad, except that BlockClosure>>assertWithDescription: sends #logFailure: which is only implemented in TestCase .... Soooo, it appears that assertWithDescription: should only be sent from instances of TestCase (and send removed from RxMatcher>>split:) or the send of #logFailure: removed from BlockClosure>>assertWithDescription: ... Found this on in GemStone testing while trying to figure out a test case that would trigger a failure of #assertWithDescription:, which BTW, I couldn't do .... so the #assertWithDescription: is probably unnecessary (or we need a test case to trigger the assertion)...