Review every automated run across your frameworks, pipelines and systems in one place. When it’s time to release, bring the results, remaining manual checks and approvals together. Keep a record of what was tested and approved.
Keep your test frameworks. No time limit on the free plan.
See the 5-minute setup. No need to define automated test cases first.
Review results in Tesults, query them from your AI agent, or use them in your CI pipeline.
Automated test evidence · Build 2.8.0
Trusted by teams at
“Tesults is our dashboard of choice. We’ve rolled it out to the team.”
“This is wonderful! The APIs and integrations are very useful for us.”
“Brings the fruits of test automation to life.”
Start with your automated results. Review failures, complete the remaining checks and record the evidence for the release.
Your web, API and service tests already run in different places. Send their results to Tesults so the team can review failures, logs and history without piecing together separate reports.
Tesults highlights differences between test runs and flags flaky tests from their history. Review new failures, inspect errors, logs and screenshots, and see which tests have recovered before deciding what needs to be fixed.
Manage reusable manual test cases, assign tests and record the results. Use release checklists to review automated and manual runs alongside tasks such as confirming a rollback procedure. See what still needs doing before, during and after deployment.
Attach automated and manual test runs to a release record. Collect team approvals and seal the record when the release is complete. Keep the results that supported the decision, even as testing continues on the next build.
Connect the Tesults MCP server to Claude Desktop, Claude Code, Cursor or another MCP-compatible client. Your agent can query uploaded test results and history without you copying logs into chat or checking each dashboard.
Configure the MCP server with a Tesults API token, then ask about failures, flaky tests or regressions. The agent calls Tesults tools to retrieve the evidence for its answer.
Query the Insights API directly from your own tools, deployment checks or agents. Get structured results without collecting and comparing every raw test report yourself.
Retrieve a run summary, failed tests and failure patterns to guide investigation.
GET /api/insights/explain-runIdentify tests that alternate between passing and failing. Retrieve failure rates, last failure timestamps and classifications.
GET /api/insights/flaky-testsSeparate new failures from continuing failures and recovered tests. Feed the comparison into your deployment checks.
GET /api/insights/what-changedNotify the team in Slack, Microsoft Teams or Mattermost when results arrive. Create Jira issues from failed tests and update issue status from later results. Use PagerDuty to route incidents.
Review individual results and the logs, screenshots and files uploaded by your tests. Compare runs to see what changed, without collecting reports from separate pipelines.
Explore test results →
A report from one framework tells you about one part of your system. Tesults brings results from your different targets together so the team can review the broader picture, spot failures and drill into the details.
Explore the dashboardExperiences shared by Tesults customers. Individual outcomes vary.
Keep reusable manual test cases and assign them to testers. Link automated results and manual runs to release checklists, alongside your deployment tasks. When the team signs off, preserve the test results and approvals in a release record.
Start by collecting automated results. Add manual tests, checklists and release records as your team needs them.
Playwright
Cypress
pytest
JUnit 5
Jest
Robot Framework
NUnit
GoogleTestXCTest
Postman
TestNG
Mocha
TestCafe
WebdriverIO
Protractor
RSpec
Jasmine
CodeceptJS
Nightwatch
Vitest
Waffle
colcon
ROS 2All integrations & custom frameworks →Use a Tesults language library to upload results from your own test systems, or submit results through the REST API.
Access your test results and dashboards with the Tesults mobile app for iOS and Android.
No. Keep your existing frameworks and CI pipeline, and add a Tesults integration to send results. You don’t need to create automated test cases in Tesults before uploading results. See the integration guides.
Manage reusable test cases in Lists and execute them in Runs. Link manual runs and automated test targets to release checklists for review. Attach test runs to a release record to preserve the results and team approvals. You can use these together or start with the parts your team needs.
Yes. Alongside integrations for popular frameworks, Tesults provides libraries and an API for submitting results from your own test systems. Explore the integration options. Missing an integration? Contact us for help connecting your framework.
Yes. Tesults provides dashboards and detailed results in its own interface, so team members can review uploaded test results without navigating each pipeline’s separate reports.
Yes. SAML 2.0 and Google OAuth are supported, and SSO is included on the free plan. See the SSO configuration guide.
Yes. Export test results and saved test lists to CSV, or retrieve results through the API for use in your own systems. Export test lists or read the results API guide.
Yes. There is no time limit on the free plan. Compare plans and limits to choose what fits your team.
On paid plans, Tesults charges for active users only and automatically stops billing for inactive users. You do not need to manually remove unused seats. See the Fair Billing Policy and pricing and plan limits.
Review your automated results, complete the remaining checks and keep the release record.
No time limit on the free plan.
C++
Rust
Java
C#
Python
Ruby
JavaScript / Node.js
Go
Kotlin
PHP
Swift