Investigate test history with AI
Connect your coding agent to the Endform MCP server, then ask questions about the test history for the repository you are working in. The agent can compare trends, inspect individual executions, compare a failed attempt step by step with a passing run, and link you to a replay of what it found, without you copying data out of the dashboard.
The conversations below are representative examples. Your results will use your own tests and Endform history.
Example conversationWhat are our flakiest tests?
Tool call:
analytics_querypassing test runs with retries, grouped by test, last 7 daysTool call:
samples_queryrecent retried executions of the flakiest testTool call:
test_attempt_inspectcompare a failed attempt with its passing retryTool call:
test_attempt_inspectcheck another failed attempt of the same testTool call:
test_attempt_replay_linkreplay the failed click beside the passing retryExample conversationWhich tests are slowest?
Tool call:
analytics_queryaverage test duration grouped by test, last 30 daysTool call:
samples_queryrecent executions of the slowest testsTool call:
analytics_querydaily duration trend for the leading slow testExample conversationTriage today's failures
Tool call:
analytics_queryfailed test count grouped by test, last 24 hoursTool call:
samples_querylatest failed executions and their ordered attemptsTool call:
test_attempt_inspectinspect a representative checkout failureYou can make these questions more specific by naming a branch, commit, Playwright project, test file, title, or time window. The complete historical data tool reference is in Endform MCP server.