Hi, Is there a way to instruct MbUnit to not treat Main methods as tests? Ideally I'd like to place an attribute such as [Skip] in front of every Main method which won't prevent it to function as expected outside of MbUnit.
My co-workers often need to step through the tests they write in the debugger. Many choose to create a class with a main method which calls the "Constructor, Init, Test1, Destroy, Init, test2, Destroy, ..." sequence. They often check in those classes, which adds redundant information to the results of a nightly test run. Even if there is a better way to debug the tests, it won't be easy for me to convince them. The project with tests compiles as a stand-alone executable, so, if there exists some sort of a switch, I would have to do it in code (not as a command-line argument). I've heard that I can write my own MbUnit attribute. To do that, would I have to modify the source code of MbUnit, or can I just use the installed binary version and add customization on top of it? If I have to modify the source, then where can I get it? I looked for it several weeks ago and could not find anything. Thanks. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
