Get Test Run Timeline
get_test_run_timelineReports the true first and last execution times for a test run, including duration and active days, instead of relying on administrative created and locked timestamps.
Instructions
Reports when testing in a test run actually started and finished.
Use this instead of comparing a run's createdAt to its lockedAt. Those two bracket the run's administrative life, not its testing: a run is typically opened before anyone executes against it and locked well after the last result, so the gap between them can be twice the real duration.
This reads the per-execution timestamps Tuskr keeps on each test case and keeps only those recorded against this run, giving the true first and last execution, the span between them, and how many distinct days saw activity.
For a recent run, get_test_run_details is the cheaper way to get the first and last result times and the duration: one small call, where this tool fetches every results page untrimmed (100 cases per page). Use this tool when those timestamps come back null (Tuskr may not have recorded them for older results), or when you need the number of distinct days with activity, the daily breakdown, or the cases that were never executed.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| test_run | Yes | ID of the test run. This is the UUID after /test-run/ in the Tuskr URL. The underlying endpoint addresses the run in the URL path, so a run name or R-key is not accepted; resolve one to its ID with list_test_runs first. | |
| include_daily_breakdown | No | if True (default), adds executionsByDay, a map of date to execution count. Useful for telling a run worked steadily over a week from one tested in an afternoon after sitting idle. Its size is bounded by the run's span, so it stays small. Days are bucketed by UTC date, so an evening session in a UTC+2 or later timezone can straddle two buckets and read as two days of activity. |