#21 problem with assertEquals

[Jos]

If you add a third parameter to assertEquals, you can
hang the unit testing framework.

I'm currently using it with the pause()/resume()
functions for async code testing.

i'm in a async callback function, so i've already
called pause(). I mistakenly called
assertEquals("blah", x.value, true). It should only
take 2 params, but the complier didn't complain about
the extra argument, and, when compiled, the program
hung at that assertion.