I'm about to release MSpec 0.5 with a couple of fixes and the ReSharper 6.1
EAP runner.
There's a little breaking change in this release that I wanted to let you
know about upfront:
ShouldBeEmpty behaves differently for null strings. In previous versions a
null string was considered empty. Starting with version 0.5 this is no
longer the case and
string foo = null;
foo.ShouldBeEmpty();
will throw an exception.
You can read more about this rather long-standing issue here:
https://github.com/machine/machine.specifications/issues/6
Cheers,
Alex
--
Alexander Groß
http://therightstuff.de/