We've built out numerous Extension Methods to our domain model that houses our assertion logic. This gives us some very nice reuse across our unit tests, but the problem we're now running into is when a test fails, the location of the failed test is obfusticated by this technique. We're using TestDriven.NET and we can no longer double- click the failed test in the Errors window of Visual Studio and be navigates to the failing test. Instead, you're navigated to the assertion extension method. The more logic we centralize, the harder it is navigate our test code.
I thought I remember reading about an attribute I can decorate our assertion extension methods to make MbUnit ignore them? I've tried [DebuggerHidden] and [DebuggerNonUserCode], and neither do the trick. Any tips? thanks -kelly --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MbUnit.User" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/mbunituser?hl=en -~----------~----~----~----~------~----~------~--~---
