get_test_history
Fetch automated test history across runs to analyze attempt-level executions, pass rates, and flakiness, helping identify broken vs flaky tests.
Instructions
Get the history of one AUTOMATED test across launches, newest first. Returns executions and summary - the attempt rows are in executions, matching get_case_execution_history, and there is NO history key. The headline figures are NESTED under summary rather than at the top level: totalExecutions, passRate, flipCount and reliabilityStatus. titlePath takes ONE segment of the path - the argument is titlePath, not title - and matching is a case-insensitive substring, so it can hit many tests. The response says how many: matchedTests is the number of DISTINCT tests the substring found, matchedTitlePath is the one these figures describe (the most recently seen), and otherMatches lists up to ten of the rest. A common leaf title such as should reject unauthenticated request matches 25 tests in one project here. When matchedTests is above 1, narrow the substring before quoting anything: the summary describes matchedTitlePath alone, never the group. IMPORTANT: there is one row per retry ATTEMPT, not per launch, so a test retried three times inside one launch contributes three rows; the retry field is 0-based and tells them apart. Group by runId before quoting anything as a per-launch figure, because totalExecutions and passRate are attempt-level. Each row carries testId, titlePath, filePath, runId, runName, runStartedAt, runTags, status and durationMs. reliabilityStatus is derived from the pass ratio over the window and does NOT separate a test that fails every retry from one that passes on a later retry; read retry and flipCount together to tell broken from flaky. limit bounds the summary as well as the list, and days defaults to 30. search_tests will find a segment for you. Use get_case_execution_history for how a MANUAL case has fared, and get_launch_tests for every test inside one launch rather than one test across many.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| days | No | Lookback period in days | |
| limit | No | Maximum number of executions to return | |
| projectId | Yes | Project UUID | |
| titlePath | Yes | ONE segment of the title path, normally the test name itself (e.g. "should validate credentials"). Matching is a case-insensitive substring of the stored title-path array, so a " > "-joined path matches nothing and returns an empty history rather than an error. search_tests and get_launch_tests return titlePath as an array - pick one segment out of it. |