http://wikipedlla.com/assertions_going_unhandled_by_mbunit_when_using_parameterized_run_invokers > Hey everyone, > I'm trying to build a custom extension to MbUnit to execute CppUnit > tests and mirror the results into MbUnit test hierarchy. In order to > do so, I've created a custom run invoker to execute tests using a > cppunit runner. > Now the interesting part... when I add an Assert.Fail() statement into > my run invoker' Execute() method, the AssertionException thrown is > never caught / handled by MbUnit. As I suspected my code might be > flawed, I tried downloading Jay Flower's XHtml extension sample > solution (http://jayflowers.com/WordPress/?p=88) and found the same > behavior running the 2.4 release. In a weird twist, it seems that if > you comment out the following line: > public override object Execute(object o, IList args) > { > foreach (Object Arg in this.Args) > { > // args.Add(Arg); /* > Including an argument somehow makes > MbUnit not handle the assertion exception. */ > } > return base.Execute(o, args); > } > The assertion is caught by MbUnit. > Does anyone have any insight into why MbUnit is exhibiting this > behavior? Am I missing some crucial logic for handling these cases > correctly? > Any help that can be provided would be much appreciated. > Cheers, > -A
--~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
