Re: How do I debug break in case of assertion failure?

No, it's an entirely different mechanism.
 
Going into debug every time you have a failure sounds like a misuse of the
test framework to me. If your tests are sufficiently small in scope, test
only
one thing and are well-named, you will almost always know where the 
problem lies when you get a failure. You should see your need for using
the debugger decline.
 
Charlie


  _____  

From: Igor Gatis [mailto:[email protected]] 
Sent: Wednesday, August 06, 2008 6:34 PM
To: Charlie Poole
Cc: [email protected]
Subject: Re: [Nunit-users] How do I debug break in case of assertion
failure?


I'm wondering if Assert.XXX() functions call
System.Diagnostics.Debugger.Break() if the user wants to. Is such mechanism
available?


On Wed, Aug 6, 2008 at 5:27 PM, Charlie Poole <[email protected]>
wrote:


If you use Visual Studio, you can tell it to break as soon as an
AssertionException
is thrown. Other IDEs will probably have similar functionality.
 
Charlie


  _____  

From: [email protected]
[mailto:[email protected]] On Behalf Of Igor Gatis
Sent: Wednesday, August 06, 2008 1:38 PM
To: [email protected]
Subject: [Nunit-users] How do I debug break in case of assertion failure?



When an assertion fails, I'd like to start my preferred debugger. How do I
enable that?

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

_______________________________________________
Nunit-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nunit-users