In MbUnit v2 a test decorator can only effect changes to the test method that it wraps.
In MbUnit Gallio, the effective "scope" rules are somewhat more relaxed. A decorator can modify other participants in the test tree including parents and children of the node being decorated. It's not recommended but not prohibited either. However, the case of wrapping "the whole process" in Gallio is simplified because the SetUp and TearDown processes belong to the tests themselves. So a test decorator can just add behavior around the SetUp and TearDown for that particular test. Jeff. -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Seth A. Roby Sent: Thursday, August 30, 2007 7:56 AM To: MbUnit.User Subject: MbUnit Re: DecoratorPatternAttribute On Aug 29, 5:36 pm, "Jeff Brown" <[EMAIL PROTECTED]> wrote: > You pretty much have the right idea. It would indeed be a pain to set > up. Sorry.. I'll add your suggestion to the list for Gallio. That'd be great. Thanks. > > Gallio decorators can actually have non-local effects upon the test > tree so the behavior you want is already possible there. But it > wouldn't hurt to optimize the case to make it easier. What exactly do you mean by 'non-local effects'? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
