|
|||||||||||||||||||||||||||||||
CategoriescsUnit supports categorization of tests. Basically this means you can assign categories to tests and test fixtures, and then use the categorization for instance for selecting tests. If you don't need this feature right now you can safely ignore it for now by jumping to the next topic. This is one of the design principles we try to follow wherever possible. If you assign one or more category to a test or a test fixture, please be aware of the following rules:
Once you have defined categories for your tests you can then select categories in the graphical user interface. When you then save your settings as a recipe, the category selection will be save along with it. After that you can supply the recipe to csUnitCmd, e.g. for inclusion in your automated build. The category selector is part of csUnit's runtime environment regardless of the front end. Category HierarchyBoth TestFixture and Test support categories. As the Test methods are always contained in a TestFixture, and as both can be assigned to one or more categories, there are more scenarios to be explored. Let's take the following two test fixtures: [Fixture(Categories = "DB")] [Test(Categories = "MSFT")] [Fixture(Categories = "DATA")] [Test(Categories = "MSFT")] [Test(Categories = "Oracle")] There are now several scenarios possible, and depending on which categories you include or exclude, a different set of tests will be executed.
The easiest way to include or exclude categories is through the graphical user interface of either csUnitRunner or the addin. Alternatively you can edit the recipe directly, which is an XML file and also includes the settings for the Category Selector. |
Prerequisites And Target Environment Sponsors:
|
||||||||||||||||||||||||||||||
Copyright © 2002-2008 by Agile Utilities NZ Ltd. All rights reserved. Site design by Andreas Weiss. This site is protected by bot traps. |