Closed dmoonfire closed 9 years ago
Aha! You're using the 2.0.6 alpha version. That was a quick and dirty release to add some logging for someone, and I mucked up some logic. I've fixed it locally, but had forgotten about that release. Guess who didn't run the tests before a release!
It's relatively harmless - it'll just run pretty much all tests every time, so not ideal, but shouldn't be anything worse than that. I'm currently rewriting the message handling, and I'm currently down to just one failing test, so there should be a new version soon. And of course I'll test this before the release, too.
I have a class with three [Fact] tests inside it. They all use a common function that was throwing an exception (from another namespace, if that matters). It doesn't matter which one I debug (either via C-u C-d or select the test and click the debug), but it runs all three of them one after the other. It also runs in a consistent order, so I had to fix them in an suboptimal order. :)
I double-checked that "update" didn't list any new features. Below is the detail from the Resharper about menu. I'm using Visual Studio Ultimate (detail is below ReSharper).
And Visual Studio's: