Just my 2-cents -- I was never a big fan of
#assert:equals:description: because it puts additional String literals
into the CM instances which... don't seem very useful -- because even
after I read the description I still have to read and understand the
code, which what you have here is not too complicated and, if it were,
the work should go into simplifying it rather than explaining it..  :)


On Tue, Aug 14, 2012 at 5:37 AM, Frank Shearar <frank.shearar at gmail.com> wrote:
> On 14 August 2012 11:35,  <commits at source.squeak.org> wrote:
>> Frank Shearar uploaded a new version of ToolsTests to project The Inbox:
>> http://source.squeak.org/inbox/ToolsTests-fbs.54.mcz
>>
>> ==================== Summary ====================
>>
>> Name: ToolsTests-fbs.54
>> Author: fbs
>> Time: 14 August 2012, 11:35:27.936 am
>> UUID: 308456b2-b9bf-428b-a698-9041cf4c29d9
>> Ancestors: ToolsTests-fbs.53
>>
>> assert:equals:description gives better error messages for failing tests.
>>
>> =============== Diff against ToolsTests-fbs.53 ===============
>
> In particular, this test fails on the build server but not locally
> (off what's hopefully an identical image). I'm hoping the extra
> diagnostics will tell me what's going on there. And, of course,
> assert:equals: is better than assert:. But that goes without saying.
>
> frank
>