Bugs Found While Writing Specs

Bugs Found While Writing Specs

So, sometimes something surprising happens when you're writing specs for software which is already written, AND seems to be working fine. Sometimes, you find out that it's not quite as infallible as you think. Below are some of the notable OOPS! moments we've run into when writing specs.

• Garbage Collector doesn't fire the willFree method on an object when it is recycled. Even after setting the maximum recycled objects size to 0 and 1 it still won't fire.
• Message objects compare equality based on pointer value. This was a facepalm moment for me. If message(a) is not equal to message(a) then which way is up?
• Blocks with formal arguments substitute nil in place of a formal argument when not supplied. There was a time when this would result in an exception. I'm not sure where it broke, but it broke.