gsinclair/whitestone — Issue #4: Failure message for N! could read better
Author: gsinclair
Created: 2012-02-26 01:20:32+00:00
State: open

Given the assertion

N! tl1.description

it failed with the message

Condition expected NOT to be nil

That's fine, except that I didn't give it a condition, I gave it a value. So the message would read better:

Condition or value expected NOT to be nil

Maybe it could even be sensitive to what was passed in -- a condition or a value -- and tailor the failure message to that.

(A "condition" is something passed in braces, like `N { foo.bar }`)