Debuging failing tests

[bob]

Hello,
I've tried a few testing frameworks with C# but so far haven't found a
way to debug into a failing test. I'm used to S Unit (Smalltalk)
where when a test fails you just right click on it and say debug and
the program halts at the point where the test fails. This makes it
very easy to debug the test as you have the stack, locals etc. At
them moment I'm having to recompile the main loop to call the failing
test and put a break in at the point of failure, which clearly is a
nightmare.

Can anyone help?

Thanks in advance

bob

[Nicole Calinoiu]

Bob,

If this is in VStudio.NET, you can break into the debugger by configuring
the IDE as described at
http://msdn.microsoft.com/library/en...exceptions.asp.

HTH,
Nicole
"bob" <bo**********@hotmail.com> wrote in message
news:b0**************************@posting.google.c om...

Hello,
I've tried a few testing frameworks with C# but so far haven't found a
way to debug into a failing test. I'm used to S Unit (Smalltalk)
where when a test fails you just right click on it and say debug and
the program halts at the point where the test fails. This makes it
very easy to debug the test as you have the stack, locals etc. At
them moment I'm having to recompile the main loop to call the failing
test and put a break in at the point of failure, which clearly is a
nightmare.

Can anyone help?

Thanks in advance

bob

[bob]

Hi Nicole,
I tried your plan but I couldn't work out what exception was fired.
I'm using CSUnit's Assert like this:

Assert.True(false)

I can't really understand how people debug their tests without the
stack so it must be possible.

Bob

"Nicole Calinoiu" <ni*****@somewhere.net> wrote in message news:<#e**************@TK2MSFTNGP11.phx.gbl>...

Bob,

If this is in VStudio.NET, you can break into the debugger by configuring
the IDE as described at
http://msdn.microsoft.com/library/en...exceptions.asp.

HTH,
Nicole
"bob" <bo**********@hotmail.com> wrote in message
news:b0**************************@posting.google.c om...

Hello,
I've tried a few testing frameworks with C# but so far haven't found a
way to debug into a failing test. I'm used to S Unit (Smalltalk)
where when a test fails you just right click on it and say debug and
the program halts at the point where the test fails. This makes it
very easy to debug the test as you have the stack, locals etc. At
them moment I'm having to recompile the main loop to call the failing
test and put a break in at the point of failure, which clearly is a
nightmare.

Can anyone help?

Thanks in advance

bob

[Nicole Calinoiu]

Bob,

This is a CSUnit issue, not a C# issue. There's already a discussion
concerning the issue on the CSUnit forum at
http://groups.yahoo.com/group/csunit/message/326.

Nicole
"bob" <bo**********@hotmail.com> wrote in message
news:b0**************************@posting.google.c om...

Hi Nicole,
I tried your plan but I couldn't work out what exception was fired.
I'm using CSUnit's Assert like this:

Assert.True(false)

I can't really understand how people debug their tests without the
stack so it must be possible.

Bob

"Nicole Calinoiu" <ni*****@somewhere.net> wrote in message

news:<#e**************@TK2MSFTNGP11.phx.gbl>...

Bob,

If this is in VStudio.NET, you can break into the debugger by configuring the IDE as described at
http://msdn.microsoft.com/library/en...exceptions.asp.
HTH,
Nicole
"bob" <bo**********@hotmail.com> wrote in message
news:b0**************************@posting.google.c om...

Hello,
I've tried a few testing frameworks with C# but so far haven't found a
way to debug into a failing test. I'm used to S Unit (Smalltalk)
where when a test fails you just right click on it and say debug and
the program halts at the point where the test fails. This makes it
very easy to debug the test as you have the stack, locals etc. At
them moment I'm having to recompile the main loop to call the failing
test and put a break in at the point of failure, which clearly is a
nightmare.

Can anyone help?

Thanks in advance

bob