It is not possible unless a major change in the assertion rationale. 'Each assertion is to throw if violated'
 
You could do a "disposable" assertion class that would record failures and check for failures when disposed.

 
On 3/31/06, [EMAIL PROTECTED] < [EMAIL PROTECTED]> wrote:

Hi, is it possible to force MbUnit not to stop on the first assertion
failure that occurs?

How can it be done?

Thanks,
Bruno.



--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to