You can assign categories to test plans, test cases, test scripts, test data, test suites, test case execution records, test suite execution records, test case results, and test suite results.
By assigning categories to your artifacts, you can set up a hierarchical directory structure that is useful for keeping artifacts organized. A hierarchical directory structure is also helpful when you need to find individual artifacts among the many test artifacts that you manage.
The following figure shows the category editor for test plans.

The process of organizing with categories starts by defining the category hierarchy, which is composed of categories, category values, and subcategories. Each category can contain one or several category values, and subcategories and values. Many artifact types include default categories and category values that you can supplement or replace. For example, the default categories for test plans are Product, Release, and Iteration.
The following table shows a few sample categories and category values for test plans.
| Category | Category value |
|---|---|
| Product | Personal Banking |
| Personal Investing | |
| Release | 1.0 |
| 2.0 | |
| 3.0 | |
| Build | 041511 |
| 041611 | |
| Iteration | Developer Test |
| Integration Test | |
| Performance and Service Level Test | |
| User Acceptance Test | |
| M1 | |
| M2 | |
| Location | RTP |
| Zurich | |
| Guadalajara |
After you define categories and category values, you can further define a hierarchical organization of artifacts by establishing category relationships. You can set up a parent-child relationship by defining subcategories. For example, in the following image, the Release category has the values of 1.0, 2.0, and 3.0. Furthermore, those values have specific subcategories, such as Iteration and Build.

You can also designate a category as required. In that case, you cannot save until the required category value is assigned. An asterisk indicates a required category.
You can also designate a category as multivalued. When a category is multivalued, you can assign multiple category values to a test artifact. For example, you might want to indicate that a test plan is to be used for both Iteration 1 and Iteration 2.