get_testcase_details
Retrieve detailed information about a test case, including error messages, code snippets, and execution steps, to debug failures and understand how the test executed.
Instructions
Get detailed information about a specific test case. You can identify the test case in two ways: 1) By testcase_id (can be used alone), or 2) By testcase_name combined with testrun_id or counter (required because test cases can have the same name across different test runs). Returns error message, code snippet, file location, test steps per attempt, console logs, and optional artifacts (screenshots, videos, traces). Use steps_filter='failed_only' to return only steps that errored, stripping passing setup/hook steps. Use this to debug why a test failed or understand how it executed. Example: 'Get test case details for "Verify user can logout and login" in testrun #43'.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number for pagination (default: 1). | |
| limit | No | Max results to return (default: 1 for ID lookup, 50 for search, max: 1000). | |
| counter | No | Test run counter number. Alternative to testrun_id to identify the test run. Example: 43. | |
| get_all | No | Return all matching results up to 1000 (default: false). | |
| sort_by | No | Sort results by field (default: startTime). | |
| by_status | No | Filter by test case status. | |
| projectId | Yes | Project ID (Required). The TestDino project identifier. | |
| sort_order | No | Sort direction (default: desc). | |
| testrun_id | No | Single test run ID to filter results. Example: 'test_run_6901b2abc6b187e63f536a6b'. | |
| testcase_id | No | Test case ID. Can be used alone to get test case details. Example: 'test_case_123'. | |
| testrun_ids | No | Multiple test run IDs (comma-separated, max 20). Example: 'test_run_abc,test_run_def'. | |
| steps_filter | No | Filter steps in each attempt. Use 'failed_only' to return only steps with errors, stripping passing setup and hook steps. | |
| testsuite_id | No | Filter by test suite ID. | |
| history_limit | No | Max number of history entries to return (default: 10). | |
| testcase_name | No | Test case title (partial match, case-insensitive). Must be combined with testrun_id or counter when used alone. Example: 'Verify user can logout and login'. | |
| include_traces | No | Include Playwright trace links from test attempts. Default: false. | |
| include_videos | No | Include video recording URLs from test attempts. Default: false. | |
| by_code_snippet | No | Search in error code snippets (partial match, case-insensitive). | |
| include_history | No | Include historical executions of the same test case when searching by name. Default: false. | |
| by_error_message | No | Search in error messages (partial match, case-insensitive). Example: 'Timeout 15000ms exceeded'. | |
| include_artifacts | No | Include all artifacts (screenshots, traces, videos, attachments) with authenticated URLs. Default: false. | |
| testcase_fulltitle | No | Full test case title including suite path (partial match, case-insensitive). Example: 'auth.spec.js > Login > Verify user can logout and login'. | |
| include_attachments | No | Include all attachment metadata from test attempts. Default: false. | |
| include_screenshots | No | Include screenshot URLs from test attempts. Default: false. |