Library health¶
Library health identifies test cases that may benefit from a human review. It does not change data and does not use an AI provider.
Open Library health in the Web report catalogue. The test library can preselect a unit with its visible child units or one test case. The Windows entry opens the same Web report; authentication and project permissions also apply there.
Scope and hints¶
Only library units and test cases you may view are checked. A use is counted only when you can also view its plan, its run when applicable, and the planned test case. No visible plan/run usage and no recorded execution visible therefore refer solely to your visible scope. They do not authorize deletion or describe usage throughout the project.
The initial age threshold is 180 days, adjustable from 1 to 36,500 days. Long time since recorded change uses the latest recorded modification of the test case, its variants and Quick rows/cells when applicable. The threshold includes the cutoff date, using the server's calendar day. Missing dates remain unknown. Age does not establish whether content is current; changes to linked reusable step blocks are not assessed as a separate modification history.
Other hints identify empty titles, missing variants, or a standard variant without effective steps or an expected result. Inherited text and the structured step content stored in variants are considered. Quick tests are checked for cell content instead; empty standard text fields are not a hint for a Quick test. Prerequisites are optional.
Select a hint filter and choose Check library. The table shows matching test cases, their reasons, visible use counts and their last dated visible execution. The case title opens the evidence in the library. The matching count is a count of test cases, not hints; multiple reasons can apply to one case.
Limits and API access¶
One capture checks up to 2,000 visible test cases and 20,000 visible uses. It checks up to 200 variants per case and 1,000 rows per Quick variant. A reached limit is explicitly shown as a partial result. Incomplete usage suppresses negative usage/execution hints; incomplete content suppresses negative content hints for the affected case. Filters and page navigation capture the current state again.
MCP and the HTTP/JSON REST API use the same read-only operation and permissions. Its contract includes capture time, stable reason codes, limits, completeness and paging. An API key needs the corresponding read permission and project association. API access does not extend object permissions.