What's new in Machine.Specifications 0.5.12, 0.5.14, 0.5.15, 0.5.16
91 views
Skip to first unread message
Alexander Groß
unread,
Sep 3, 2013, 5:26:30 AM9/3/13
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to machin...@googlegroups.com
0.5.12:
ReSharper 8 support
dotCover 2.5 support by Alexander Mikhailov
Documented --filters parameter for mspec.exe by Pieter Germishuys
Fix for TeamCity integration by James Crowley
0.5.13: was not released
0.5.14:
Closed #146: MSpec doesn't fail when Machine.Specifications cannot be found for a spec assembly. Can be useful if you want to target mspec.exe to a NUnit assembly, which is now a no-op.
Closed #151: Fixed MSpec slowness with ReSharper 8.
0.5.15:
Fixed an issue with running two spec assemblies: When the first one fails and the second one succeeds mspec.exe reported success. I needed to introduce a breaking change in the runner, so older versions are not compatible with 0.5.15. Update your ReSharper runners when upgrading to 0.5.15!
0.5.16:
Capturing standard out, standard error and trace streams in ReSharper 8 (7 does this for us) and the console runners. Output is added to the test result XML/HTML. (#158)
Some fixes for behaviors in ReSharper (#155)
Sorry it took so long this time. I'll add a history.txt to each future release.