@testomatio
Account based inUkraine
About this account
- Account based in
- Ukraine
- Connected via
- Ukraine App Store
Account-level information from X, not a live location or the device used for a specific post.
We organize testing so you would actually enjoy building quality products.
Joined May 2020
- Tweets1K
- Following157
- Followers1.5K
- Likes1.3K
Pinned Tweet
New release from Testomat.io! Dictate test documentation, run manual tests directly from your browser, and build richer integrations with Public API v2 🚀
Here's what's new 👇
• 🎙 Voice Mode — dictate test steps, requirements, comments, and exploratory testing notes
• 🧩 Testomat.io Browser Extension — create tests, record browser actions, and execute manual runs without switching tabs
• 📊 Manual-to-Automated Analytics — track how your test suite’s automation coverage changes over time
• 🤖 AI-generated project structures + Mermaid diagrams for visual test design
• 🔌 Public API v2 improvements — branch-aware requests, aggregated counts, run statistics, analytics access, and clearer pagination
• ✨ Easier manual run editing, search within Test Plans, advanced relaunch improvements, and more!
Reliability isn’t only about the product.
If the same test passes and fails on unchanged code, the test suite is part of the problem too.
This guide explains how to measure reliability, from MTBF and recovery time to flaky tests and repeated AI agent runs: testomat.io/blog/reliability…
Mercury 2.5 generated tokens 9× faster than GPT-5.6 Luna. The full Explorbot session? Same time as before.
The bottleneck was page reading, not planning.
@davert ran it as the planner in a real browser-testing agent. Why tokens/sec can mislead you 👇
A failed test from an AI agent does not always mean your product is broken. Just as often it means the agent did not understand the screen.
So a run here ends with three outcomes instead of two: defect, not a defect, and could not complete.
The summary keeps them apart, and the third one says something about the agent, not about your product.
Most tools file that third case under "failed".
That is what turns a report into noise, and it is why teams stop opening AI-generated results after the first week.
On our own product, a person opens every failed run, watches the video, reads the steps the agent tried and the console output, and then decides. Nobody should trust an agent blindly, and we do not ask you to.
When you run exploratory testing by hand, clicking is the cheap part. Writing everything down is what eats the time.
You click through a screen, watch what happens, then stop and take notes. If you want logs from that session, you set up something separate to capture them. The write-up comes later, from memory and screenshots.
Explorbot produces all of it on its own: the notes, the logs, the video, and every step it tried, attached to a run in Testomat.io. Your engineer spends that time reading the report instead of writing it.
Postman is the default API client. That doesn't make it right for every team.
Need Git-native storage, self-hosting, code-first tests, or AI agents?
@davert compares 7 alternatives and the workflows each one fits 👇
Emulator tests passed. Then checkout crashed on a real device.
OS versions, network drops, incoming calls, battery — CI doesn't see any of it.
Our CEO @mpoliarush building a mobile testing strategy around risk instead of the biggest device matrix you can afford 👇
Explorbot uses three model slots:
model — reads the page
agenticModel — plans and judges
visionModel — interprets screenshots
Same model in all three, or three different ones. Routing is part of the runtime, so you can balance reasoning quality, latency and cost.
github.com/testomatio/explor…
Happy Tester’s Day from Testomat.io! Today, we celebrate the people who question assumptions, explore every edge case, and make each release more reliable 🚀
Behind every great product is a tester who challenged it, broke it, and helped the team build it better.
Thank you to all QA professionals for your curiosity, persistence, and commitment to quality. Happy Tester’s Day! 💙
An agent that waits for "Continue" is still using your attention.
Explorbot runs the whole loop: schedule, plan, execute, record, report. The team reviews the finished session instead of directing every browser action.
Scheduled runs are in early access: github.com/testomatio/explor…