← Back to all sparks
T

Testomat.io

INFRA · APIS
Velocity2.5

Testomat is closing the loop from failing test to tracked defect, one quarterly digest at a time

test-managementdefect-trackingagent-nativemcpanalytics
Current state
Testomat ships in large periodic digests rather than continuous drops, and each one pairs a structural addition with a batch of interface work. The August release adds a per-project Defects page listing the bug-tracker issues raised against failing tests, plus defects in analytics, milestone insights, and comment mentions. Underneath it, the past year laid down Requirements, Milestones, a Public API v2, and an MCP server.
Where it's heading
Two arcs run in parallel here. One is structural test management — Requirements, Milestones, tree navigation, plans — filling out what a QA team needs to run a release cycle rather than just store cases. The other is machine access: an MCP server, a v2 public API, AI quality review, AI test-data suggestions, and an analytics chat, which together make the test corpus readable by something other than a person clicking through the UI. Defects is where the first arc finally reaches the bug tracker.
Prediction
The next digest most likely deepens the defect loop, linking defect state back to test status or analytics, since that is the newest structural piece and currently a listing rather than a workflow. The API and MCP thread points at more agent-facing surface, though these entries do not indicate what it would cover.

Recent moves

  1. 6d ago

    Defects Board, Defects in Analytics, Milestone Insights, Comment Mentions, and More

    A per-project Defects page collects the bug-tracker issues raised against failing tests, alongside defects in analytics, milestone insights, and comment mentions. It connects the structural test-management work to the tracker where failures actually get resolved, which is the gap the platform had left open.

    View source ↗
  2. 1mo ago

    Tree View for Runs and Plans, Scheduled Runs, AI Test Data Suggestions, and More

    Hierarchical tree navigation for plans and runs that mirrors the test structure, plus scheduled runs and AI-suggested test data. Navigation at scale and unattended execution are both prerequisites for large suites, and the suggestion feature continues the assistive thread.

    View source ↗
  3. 3mo ago

    Milestones, AI Analytics Chat, Public API v2, MCP Server 2.0, and More

    The densest release in this window: Milestones for structuring work across development cycles, an AI analytics chat, Public API v2, and MCP Server 2.0. The API and MCP pieces are what make the test corpus addressable from outside the interface.

    View source ↗
  4. 4mo ago

    Suite-to-Folder Conversion, Bulk Tests Editing, and UI Enhancements

    Converting a test suite into a folder, plus bulk test editing. Reorganisation work that only matters once coverage has outgrown the structure it started with, which is a reasonable sign of where Testomat's accounts are.

    View source ↗
  5. 6mo ago

    Improved Test Plans, Shared Tests, Reporting, and UI Enhancements

    A redesigned plan screen that combines filtering with manual test selection, plus shared tests and reporting changes. Plan creation is the workflow a test manager repeats most, so usability gains there compound quietly.

    View source ↗
  6. 8mo ago

    New Requirements, Improved Test Launching, Robot Framework Support & MCP Server

    A dedicated Requirements page, improved test launching, Robot Framework support, and the first MCP server. Requirements gave the platform somewhere to anchor traceability; the MCP server was the opening move on agent access that the April release then rebuilt.

    View source ↗