Why don't you simply group test in different assemblies ? For example we usually have 2 assembly for each dll, for example:
assembly under test: Project.Core.dll assembly 4 unit-test: UnitTest.Project.Core.dll assembly 4 integration-test: Integration.Project.Core.dll HTH makka On Jul 16, 11:18 pm, Tim D <[EMAIL PROTECTED]> wrote: > My company is evaluating using mbUnit as a test runner/harness on a > customer project. > > One of the requests from the customer is the ability to run a list of > individual tests. Is this possible in v2.x or in v3 console runner? > > I understand there is the filter option on things such as category and > namespace. But the customer wants more control and assigning a > different category or building only one test per class seems tedious. > > Ideally, the customer would like to specify an XML file with list of > test cases to run. Duplicates in the list would run the test again. > I see there is the TestSuite class that allows you to build up a lists > of tests. Has someone written a plug-in to parse XML into a TestSuite > instance? > > Because of the nature of the product, using a GUI test runner is not > viable. This also means we would not be able to use TestDriven.net. > (We probably won't even have Visual Studio on the test bench). > Besides, the GUI runner does not save off the list of selected tests. > > Any suggestions on solving this or good arguments to push back on the > customer? > > Thanks, > tim --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
