Jeff, I have a few follow-up questions inline. Thanks! On 7/5/07, Jeff Brown <[EMAIL PROTECTED]> wrote: > > Wait for Gallio. Meanwhile, please post a feature request for this > behavior in JIRA. =)
Would you please provide the URL for it? > However, if you just can't wait, it should be possible to do this by > implementing a new TestDecoratorPatternAttribute that wraps the IRun for > the test with one that returns a fancier name. > > However, the test names need to exist at test enumeration time. They > cannot change while the tests are running. I am a little unclear about this part ... I suppose I can confuse the testing framework if I (A) name my tests with a help of a function that returns a random string, or (B) pause the test execution with a debugger (.net 2.0 or newer), then change the attributes of some test, then click continue, which will result in re-compilation of the changed parts and possibly running a test whose name it does not recognize. Should I be in a good shape if I do not do neither (A) nor (B), or is there something else I need to worry about? Or did I miss your point? > Also you might confuse > TestDriven.Net because it won't be able to map the name of the test to > run if you pick a single method in a test fixture to run. I am using .Net 2.0 + VS2005 + MbUnit 2.4. I had to Install TestDriven 2.0 because TestDriven 1.1 would not pick up MbUnit. With TestDriven 2.0 I can no longer select an individual file and click "Test with". I have to select the entire project, and only then I can choose the "test with ..." option. I am no expert in TestDriven or MbUnit, but it seems to me that TestDriven will get a chance to enumerate all tests before starting to run them, and so this should not be causing any problems. Am I missing something? Are you using TestDriven in a different way? Finally, I found that I do not really need TestDriven that much at least for my purposes. I can simply start MbUnit.GUI.exe and load the assembly (if it was not remembered from last use). All that TestDriven does for me is save a few mouse clicks. If I stop using TestDriven altogether, then will this potential issue not be an issue any more? Thank you! > > Jeff. > > -----Original Message----- > From: [email protected] [mailto:[EMAIL PROTECTED] > On Behalf Of Leonid Lastovkin > Sent: Wednesday, July 04, 2007 11:29 AM > To: [email protected] > Subject: MbUnit Generating name of the test dynamically. > > > Hi, > I have one project containing all of the tests. I will be running the > tests on up to eight different configurations: {Debug, Release} x > {Windows XP, Windows Vista} x {Office 2003, Office 2007} (I will compile > the project twice: once in Debug mode, and once in Release mode). > > I would like to decorate my tests such that the name of the test would > reflect the configuration. For example, a [Test] with signature "void > TryHeuristicA() { ... }" would show up as > "TryHeuristicA_WinXP_Office2003_Debug" ( I noticed that .Destory is > usually appended to the end of the test. I do not need it per say, but > do not mind it as long as the name of the test contains all of the > config info.) > > So, if I have these public methods: > // Returns "Debug" or "Release" > string GetMode() { ... } > // Returns "WinXP", "Vista", etc > string GetOsVersion() { ... } > // Returns "Office2003", "Office2007", etc string GetOfficeVersion() { > ... } // Returns, for example: "WinXP_Vista_Release" > string GetConfigInfo() { ... } > > Then how do I set it up? > > Regards, > - Leonid > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
