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

On Thu, Aug 7, 2008 at 2:39 PM, Igor Gatis <[email protected]> wrote:
> Just making this crystal clear: this is a test development time feature.
> Must be turned off during test passes.
>
> I would not call them totally separated.
>
> Let's say a test case failed. Don't you want to know what the state was
> right there?


Well when a previously passing test case fails it means that the
change I just did broke the existing test. I check what the test
tested for, look at my change, and figure out what's up. Debugger
might slow down this process.

This is not as easy when your change that broke a test involves a lot
of code or touches many classes. In that case you are better off doing
changes in smaller chunks and running related existing and new tests
as you go.

-------------------------------------------------------------------------
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=/