title: NUnit conflict with Debug.Assert
body: <p>I'm using NUnit to write unit tests for a libary a colleague of mine has written. His library contains a lot of Debug.Asserts which triggers on invalid input. When I'm writing the unit tests and give invalid input to his library, his Debug.Assert throws up a message box complaining about the bad input.</p>
  
  <p>I feel that it's a good thing that his library throws up an assert on invalid input, but at the same time I want the unit tests to cover bad input. But when I do this, the message box shows up and I have to manually click OK to continue with the remaining unit tests.</p>
  
  <p>In case it isn't clear, my problem is that the unit test process stops on the Debug.Assert. People are supposed to run their unit tests prior to any checkin and it's supposed to be automatic and should not throw up messages unless a test has failed..</p>
  
  <p>What's the "best" approach in this case?</p>