Project Managers

Seeking out project technical health reporting

Apr 11, 2018

blog-title-image

Tesults has been running the ‘setup assistant’ program for about four months now. Anyone can request setup assistance and a real person from Tesults will take care of writing integration code and getting a team setup.

Setup assistant is most often requested by QA Managers, Project Managers and Software Engineers focused on testing and automation. Project Managers are making a larger proportion of inquiries than we had expected.

This is an exciting development and it makes sense for technical health status reporting to be considered an important part of project management. Project Managers are seeking out tools beyond the standard task management and planning software with an understanding of how critical automated build and testing is to the development life cycle of the products that belong to the project.

If you are a project manager interested in setting up automated test reporting take a look at what Tesults has to offer here: https://www.tesults.com

- The Tesults Team

Latest Posts

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

How to Report Go Test Results to a Dashboard

How to Report Go Test Results to a Dashboard

Go has no reporter plugin, so reporting go test results means parsing go test -json and uploading the cases yourself. Here is the whole pattern.

How to Report Jest Test Results to a Dashboard

How to Report Jest Test Results to a Dashboard

How to send Jest results somewhere they are kept, viewable by the team, and comparable across runs, without giving up the default reporter

How to View Playwright Test Results in CI

How to View Playwright Test Results in CI

How to get Playwright results out of the CI console and into a durable dashboard, including parallel shards, screenshots, and retained history

What Is a Test Results Dashboard and When Do You Need One

What Is a Test Results Dashboard and When Do You Need One

What a test results dashboard actually does, how it differs from your CI logs and your test framework report, and the point at which a team starts needing one

Diagnosing CI Failures Automatically With an AI Failure Diagnosis API

Diagnosing CI Failures Automatically With an AI Failure Diagnosis API

How to turn a red build into a root cause, a regression list, and a deploy gate without a human reading the logs