In some cases this means trouble.
Let's look in this test:
Does this test pass or fail? It depends who you ask.
ReSharper says:
NUnit says:
The reason is that the ReSharper runner does not know the "ExpectedException" attribute of NUnit. Who knows, maybe it's just a version thing and some x.y.z version of ReSharper knows how to work with the u.v.w version of NUnit. The lesson is that when you have two clocks you never know what the real time is... What's next? get this blog rss updates or register for mail updates!
2 comments:
This appears to be fixed in later versions. I've been using it with ExpectedException attribute and its been hunky dory.
Grummle
Thanks for the important update.
Post a Comment