Rather than add an option to make "Category" mean two quite different things, I would be inclined to use an entirely different property if we needed the alternate approach in the future.Thinking about it, I have concluded that what you are asking for seems to be closest to the normal meaning of Category, i.e. it applies directly to whatever it is placed on. We'll worry about the other approach if someone actually needs it in the future.
-- You received this bug notification because you are a member of NUnit Developers, which is subscribed to NUnit V2. https://bugs.launchpad.net/bugs/785460 Title: Add Category parameter to TestCaseSourceAttribute Status in NUnit V2 Test Framework: New Bug description: By email from Oleg Gerovich: I am unable to enter bugs on Launchpad, so I'm emailing you per your request. We need the following feature (came out of discussion of bug 691129). Add Category parameter in TestCaseSource. Example: [TestCaseSource("dataList1", Category="Dev")] [TestCaseSource("dataList2", Category="Production"] NUnit should execute all tests in dataList1 if Dev category was accepted and all tests in dataList2 if Production category is accepted. That should be the default behavior. You can also add an option like "CategorySource", which can be set to "TestCaseSource" to result in default behavior or to "TestCaseData" to run tests in dataList1/2 that have category Dev/Production (this is your approach #1 in bug 691129). We are interested in the default behavior right now, so if adding the option is troublesome, it's not a big deal. Option names/values are up to you. _______________________________________________ Mailing list: https://launchpad.net/~nunit-core Post to : [email protected] Unsubscribe : https://launchpad.net/~nunit-core More help : https://help.launchpad.net/ListHelp
