Machine.Specifications 0.5.11 (and 0.5.10)

[Alexander Groß]

What's new in Machine.Specifications 0.5.11:

- Console output (mspec.exe) is now colored by default. You can disable colored output with the --no-color switch

- Added progress output for the console runner (--progress switch)

- The console runner now prints a list of failed specifications at the end of the test run (for silent, progress and verbose reporting options)

- Support for custom delegates (i.e. you can replace Establish, Because, It, Cleanup, Behaves_like) with your own versions as long as the delegate signatures match. Please note that this currently only supported for console and TestDriven.Net runners. ReSharper won't find your context/specs if you use custom delegates. See Machine.Specifications.Example.CustomDelegates for an example. -- Thanks Jonathan Dickinson!

- Fixed an issue with the ReSharper runner and generic Behaviors like

Behaves_like<Behavior<Foo>> a_blah_blah;

- Improved double-click navigation for behavior specifications in ReSharper

- Dropped support for ReSharper 6.0

- Fixed bug #17 which caused ReSharper to run IAssemblyContexts for each specification in an assembly (now the behavior is the same as with the console runner - running them once per assembly)

- Matt Ellis contributed code that allows you to filter for "unit test usages" in ReSharper -- thank you!

And, because I forgot to publish release notes 0.5.10...

What's new in Machine.Specifications 0.5.10:

- ReSharper 7.1 support

- Various fixes for ReSharper

- Retrieving Subject from outer class

- Context sort order

- Unimplemented specs are being reported as inconclusive

Alex

--

Alexander Groß
http://therightstuff.de/