A tool that's grown with us — easy to use, deeply configurable, and now agent-ready
We've been using SmartRuns for years now, and it's grown right alongside how our QA process has evolved. What keeps us on it is how low the barrier is day-to-day — creating a test plan, logging a run, filing a defect, none of it requires thinking twice about the tool itself. But under that simplicity there's real depth when you need it: custom fields, product areas, configurable statuses, multi-stage runs — we've been able to bend it into shapes that match whatever our process looked like at the time, rather than the other way around.
The Jira and GitHub integrations are what actually tie it into our daily workflow. The Jira plugin means tickets and test plans stay linked without manual bookkeeping, and the GitHub comment automation means PR context (what changed, what's covered) shows up where developers are already looking. And when we need metrics — pass rates over time, defect finding trends, whatever question comes up — the data's sitting in BigQuery, so we can just query it directly.
More recently, the MCP support has been the most useful addition for us — it lets AI agents read and write directly against our actual test plans, runs, and defects instead of working off some exported snapshot. Our agents can check what's already covered before writing new tests, or file a defect with real context attached, all in the same system the humans use.
In summary, a great tool that will cater to any development and quality team, regardless of their size, if they need ease of use, integration with common tools and QA traceability and accountability.

