User's Guide > About the User's Guide > Codebeamer QA: Test Management > Filtering in the Coverage Browser
Filtering in the Coverage Browser
The filtering criteria available in the coverage browser are shown in the following image:
The following filtering criteria are available in the coverage browser:
Coverage—Filters the items by the content of the Coverage column. Only the requirements that match the condition in the filter are shown in the tree.
Feature Stability—An item is stable if all of the last test runs of its test cases have passed. It is unstable if at least one of the last 10 test runs has failed, is blocked, and so on. Only the requirements that match this filter setting are shown in the tree.
Number of recent Test Runs shown—By default, only one test run is shown in the tree. Using this field you can display up to 10 of the most recent test runs for each test case.
Additional filters and AND/OR logic can be added on three levels for the test runs, test sets, and releases tracker, and four levels to user stories, requirement, and epic tracker with the optional second level. The four levels are as follows:
Initial level—Select the supported trackers.
Second level—Filter by the referenced trackers. This level can be enabled or disabled by selecting the checkbox.
Test Case Filters—Filter by the available fields of the selected test cases trackers.
Test Run Filters—Filter by the available fields of the selected test cases trackers.
* 
Historical filters cannot be used in the coverage browser.
Use the text box above the coverage tree to filter by the name of the requirement or test case.
The text filter is not case-sensitive. By default, it filters only the requirements-type trackers. This means that all test cases of the matching requirements tracker are shown.
However, if the Search in Test Cases checkbox is selected, the test cases are also searched and filtered. To search for only test cases, clear the Search in Work Items checkbox and select the Search in Test Cases.
The filter shows the children of the matching requirements as well, even if they do not match the filter.
Was this helpful?