search_tests
Search automated tests by title, file, or tag, and retrieve their recent execution status, pass rate, and flakiness over a configurable window to identify problem tests.
Instructions
Search AUTOMATED tests by title, file path or tag, and get how each has been doing. Each row carries titlePath (an array; get_test_history wants ONE segment of it), filePath, lastStatus, reliability, totalExecutions, passedCount, failedCount, passRate, avgDurationMs and lastSeen. IMPORTANT: days defaults to 7 here, the shortest window of any tool - a test that has not run in the last week is simply absent, which reads as does not exist rather than has not run lately. Pass days explicitly whenever the question is not about this week. The counts are of ATTEMPTS, so a retried test contributes more than one, and passRate is passedCount divided by totalExecutions on that basis; reliability is derived from the same rows, reading flaky when both a pass and a failure appear in the window. It returns NO linkage information at all, so it cannot answer whether a test is tied to a manual case: use get_test_case with includeRecentExecutions for that. Use get_test_history for one test in full detail over a longer window - it takes the segment as titlePath, where this tool takes query - and get_launch_tests for every test in one launch.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| days | No | Lookback period for recent executions | |
| limit | No | Maximum number of tests to return | |
| query | Yes | Search query (case-insensitive substring of the title-path array or the file path). Pass ONE title segment, e.g. "should validate credentials"; a " > "-joined path matches nothing. | |
| status | No | Filter by what happened in the WINDOW, not by how the test stands now, and the two ends are not symmetrical: failed selects tests with AT LEAST ONE failed attempt, while passed selects only tests where EVERY attempt passed. So a test that failed once a month ago and has been green since is returned by failed and withheld by passed. It cannot answer what is failing now. lastStatus on each row comes closest: it is the FINAL attempt of the most recent launch in the window, so a test that failed and then passed on retry reads passed. But the window is still the window - a test that has not run since it was fixed carries whatever it last did - so for the present state take the newest launch from get_launches_statistics and read it with get_launch_tests. flaky selects tests with both a pass and a failure in the window. | all |
| projectId | Yes | Project UUID |