The Tesults web app is designed for desktop browsers. Sign up and configure your project on a laptop or desktop. Use the iOS app or Android app to view results on the go.

Project Status and Triage

A new view of all your project targets and actionable test failures.

blog-title-image

A couple of weeks ago we introduced a new triage system for failing tests. So far it has generated mostly positive feedback and there will be refinement as further feedback from real usage is gained. The idea behind it is to add actionable delegation and tasking ability. Failing tests always need a member of the team to look into the issue and being able to keep track of this for automated tests seems like a natural extension of reporting.

When you click a test to view details you will see who the test is assigned to and you can also assign or reassign the test. Only failing tests can be assigned and the workflow is designed to be super simple and easy. The only manual action required is to assign a failing test, after that should the same test pass the task will be automatically cleared from the assignee's list. Want to view all of the tasks assigned to you? Click the 'user' icon on the top right menu bar. The user settings have all been consolidated with the project settings, you now click the 'cog' icon in the menu bar to access all settings.

Added more recently is a new project status view that gives you a complete understanding of the current status of your project across all targets at once. We had feedback that it was inconvenient to be unable to do this before without selecting each target from the drop down one at a time and so this new view is designed to take care of these concerns. This view is especially useful for displaying project build and test status on a team monitor.

As always contact support@tesults.com with any feedback and questions or if you are logged in use the contact form at the bottom of every page. Happy triaging!

Test automation reporting and failure intelligence

Consolidated test reporting for engineering teams. Store, track, and understand test results across every run and system.

Latest Posts

How to Group Failing Tests by Root Cause
How to Group Failing Tests by Root Cause
Why a flat list of failures is the wrong thing to triage, and how grouping failures by their underlying cause turns twenty red tests into a few real problems
How to Share Test Results With Your Team
How to Share Test Results With Your Team
Why screenshotting results into chat does not scale, and how to give a whole team live access to test results with roles, notifications, and one shared dashboard
How to Detect Test Regressions Between Builds
How to Detect Test Regressions Between Builds
How to find exactly which tests newly failed from one build to the next, instead of comparing two runs by eye, and tell a real regression from a flake
Why Do Flaky Tests Only Fail in CI
Why Do Flaky Tests Only Fail in CI
The CI conditions that turn a test flaky when it never flakes locally, and how to confirm a CI-only failure is flakiness rather than a real bug
Why Do Tests Pass on Retry but Fail the First Time
Why Do Tests Pass on Retry but Fail the First Time
What a test passing on retry is really telling you, why automatic retries hide flakiness rather than fix it, and how to see the pattern across runs
Why Cypress Tests Pass Locally but Fail in CI
Why Cypress Tests Pass Locally but Fail in CI
The environment differences that cause Cypress failures in CI, and how to tell a real bug from an environment flake
How to Track Test Pass Rate Over Time
How to Track Test Pass Rate Over Time
Why a single run cannot tell you if your test suite is getting healthier or worse, and how to track pass rate as a trend across runs so you can see the direction
How to Report WebdriverIO Test Results to a Dashboard
How to Report WebdriverIO Test Results to a Dashboard
Send WebdriverIO results somewhere durable and team-visible using the Tesults service, with the wdio.conf.js setup, enhanced reporting, and parallel run consolidation
How to Report Cypress Test Results to a Dashboard
How to Report Cypress Test Results to a Dashboard
Send Cypress results somewhere durable and team-visible using the Cypress Module API, with screenshots and videos attached and runs consolidated across CI
Why Playwright Tests Pass Locally but Fail in CI
Why Playwright Tests Pass Locally but Fail in CI
The real reasons Playwright tests go green on your machine and red in CI, how to debug each one, and how to tell a genuine failure from an environment flake
How to Detect and Handle Flaky Tests
How to Detect and Handle Flaky Tests
What makes a test flaky, how to detect flaky tests automatically instead of by memory, and how to handle them without disabling coverage
How to Report Vitest Test Results to a Dashboard
How to Report Vitest Test Results to a Dashboard
Send Vitest results somewhere durable and team-visible, with the setup details specific to Vitest, so multiple test jobs consolidate into one history you can act on