Report and analytics

The reporter sends each result to Testomat.io as soon as the test finishes. You read the report while the run continues. The team reacts to failures before the full run ends.

Attach screenshots and videos to failed test cases. The artifacts upload to S3 storage with public or private access and display in the report. You see what happened on the screen without a second run.

Test artifacts upload to your own S3 bucket on AWS, DigitalOcean, Azure, or Google Cloud. You control the access, the retention, and the cost of the storage. Every artifact stays in your cloud, under your rules.

Share a test report by a public link. Stakeholders watch the results in real time without a Testomat.io account, and the public view hides security-sensitive data. You answer status questions with a link.

Receive a notification when a run finishes: by email, Slack, MS Teams, or Jira. You define the condition for each notification yourself. The team learns about failures without a dashboard check.

Flaky tests appear on a dedicated widget automatically. You set the flakiness thresholds and decide which tests count as flaky. Unstable tests get attention before they delay a release.

The Defects Board collects defects from the latest runs, with the defect rate and defect clusters. You filter them by quantity or by date. The team sees which parts of the product produce the defects.

The Jira plugin connects tests and defects to requirements. You link tests to user stories directly from Jira and get coverage reports. Every requirement shows its test status before the release.

The report shows the exception and the full stack trace for each failed test. The trace points to the part of the code that caused the failure. Engineers locate the cause without a local rerun.

The dashboard collects data from all testing projects in the company. You track Flaky tests, Success Rate, Slow Tests, and Automation Coverage in a single view. Managers compare projects and report with the same numbers.