← Back to all sparks
T

TestingBot

INFRA · APIS
Velocity5.0

Cross-browser and mobile app testing cloud with live and automated Selenium testing

A browser grid that spent the summer becoming a team product, and is now opening itself to agents.

test-automationbrowser-griddevice-cloudai-agentsteam-accessci-integration
Current state
TestingBot runs a cross-browser and real-device cloud, and the last three months have gone almost entirely into what surrounds a test run rather than the run itself: custom roles enforced identically in dashboard and API, service accounts so pipelines stop borrowing a person's credentials, enforced two-factor authentication, comments with @mentions on failed runs, one-click filing into GitHub, Jira, Trello, Asana or Azure DevOps, and a notification inbox tying it together. The grid work continues underneath — WebRTC streaming for iOS simulators, a rebuilt web inspector, new devices and browser versions on the usual cadence.
Where it's heading
Two directions are visible. The platform is being made safe for organisations rather than individuals, which is what roles, service accounts, 2FA and audit-friendly reporting add up to. Alongside it, the grid is being made reachable by software instead of people: an Insights API exposing pass rates and flakiness, embeddable build reports for CI dashboards, GitHub checks on every pull request, and now Vibium's CLI and MCP server pointed straight at the grid over WebDriver BiDi. The AI work so far reads results — failure analysis, documentation questions — while Vibium is the first path where something other than a human-written script drives the browser.
Prediction
Expect the agent-facing path to be developed further, since supporting Vibium's MCP server without extra configuration is a small step from offering a first-party one, and expect the device and browser catalogue to keep rotating on its established cadence.

Recent moves

  1. 22d ago

    Vibium browser automation

    Vibium, an open-source browser automation tool aimed at AI agents, can now drive the TestingBot grid through its CLI or MCP server over WebDriver BiDi, with sessions returning the usual video and logs. Framework support is routine work here, but this is the first client in the window built for an agent rather than a test author.

    View source ↗
  2. 28d ago

    Samsung Galaxy Tab S11 in the real device cloud

    A Samsung Galaxy Tab S11 joins the physical device pool for live and automated testing. Routine catalogue rotation of the same kind as the iPhone additions before it.

    View source ↗
  3. 1mo ago

    Embeddable build reports for CI

    Every build gets a compact report at a stable URL that can be embedded in a CI dashboard, pull request comment or wiki without logging in. It moves results to where the team already looks, and fits the same push outward as the Insights API and GitHub checks.

    View source ↗
  4. 1mo ago

    Notifications in the dashboard

    The dashboard gains a notification inbox carrying @mentions from test comments, account alerts and the product feed. Small on its own, but it is the piece that makes the comments and mentions shipped weeks earlier actually reach people.

    View source ↗
  5. 1mo ago

    Chrome 150 and Edge 150

    Chrome 150 and Edge 150 become available across automated, live and visual testing. The browser-version treadmill that a cross-browser grid runs continuously.

    View source ↗
  6. 1mo ago

    GitHub pull request checks

    A GitHub App puts a TestingBot check on every pull request with pass or fail, test counts and a link to results, and comments failures with their video. It places the grid inside the review loop rather than beside it.

    View source ↗