Reporting

Receive automated test results immediately. Designed reporter send information in real-time. Possible access to test report results once even 1 test is executed.

To inspect a failing test you can attach to test case screenshots or a video. Upload test artifacts to arbitrary S3 compatible storage with public (default) or private access to a bucket. And allow testomat.io to display them.

Test artifacts are uploaded to S3 Object Storage bucket on AWS, DigitalOcean, Azure, or Google Cloud. So, by using external storage you get full control over artifacts.

Stakeholders do not need accounts to check test results. Share instant access to results in real-time. Public report won’t contain security-sensitive information.

Send notification about finished runs with test results once it was generated. Notification can be sent by email, Slack, MS Teams, Jira. You may define the condition of notification.

When you define your test cases by logical categories and subcategories for execution, then your test results are structured as well. Test cases or test suites can be grouped by sprint, releases, or functional decomposition.

Collaborate with team members based on your tests. Generate publicly available documentation from your project. Living docs are updated all the time you do something with tests in real-time

Aggregate your results when your Run Group contains multiple runs, test suites and tests. You are free to use different Merge Strategies which help you in analysis, such as Realistic, Optimistic, Pessimistic strategies.

Make cross-browser testing or mobile testing in sequence or in parallel execution on multiple environments. Tests executed in such a way are grouped automatically in run group and marked in the test report.

Heatmaps provide early warnings. Heatmaps are best used for software test data visualization. It clearly shows parts where defects are allocated, also data are sparsed.

Sorting tests by test execution result: passed, failed, skipped. Also, filter tests or test suites in test results by name or @tag using the lookup capability of an advanced search field.

Advanced Jira plugin provides bidirectional functionality to link tests to user stories. View test results, requirement coverage and edit scenarios directly from Jira.

No need to do extra actions to rerun manual or automated tests. You can modify existed test runs with updated results or you can re-execute only failed automated tests in CI\CD with a click on a button.

Create a task in Jira, GitHub, or Azure when a test run fails right from the test management app in one click. Track test results and monitor defect fixes without switching between systems

Trace errors in program code. Exception informs us about the presence of error. Stack trace, meaning Stack of Call directly points to the part of the code that caused this error.

Track any tests changes by using revisions and history in Run Archive or Group Archive. Diff tools provide easy visual comparison side by side so you can concentrate on review and changes.

Customize the data within each project and add relevant labels for test cases and test suites in a few clicks.

Study the summary statistics for the test runs you are interested in, and conclude on the project’s development.