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.

Easier integration with Tesults

Starting with pytest

blog-title-image

We are delighted to offer teams hands-on help with integration. In fact we often encourage it because the quality of the integration is what helps get the most value out of the reporting and analysis delivered with Tesults.

We will continue to offer hands-on help to anyone who requests it, that includes writing custom code, and we are proud to offer this assistance free to everyone, including teams trying Tesults with a free project. Increasingly, it has become clear however that there are teams that want to get onboarded faster, and do it all with self-service.

Tesults has always provided libraries for popular languages like Java, Python, C#, Node.js/JS, Ruby, Kotlin and Go, and then subsequently code snippets for popular test frameworks, including pytest, JUnit, NUnit, Mocha and RSpec. We are now going a step further. We want to make integration possible almost instantly. Tesults will begin to provide official plugins and libraries for popular test frameworks.

To start things off, we now offer pytest-tesults, a pytest plugin. Now instead of having to copy and paste code into a conftest.py file or write any custom code, developers can just perform a couple of commands and integration is complete:

pip install tesults
pip install pytest-tesults

See the pytest docs for complete details.

We hope this will help newcomers to Tesults get setup faster than ever, and make maintenance easier too.

One of the reasons we have held off from doing this in the past is to avoid having to be opinionated on any particular way to setup your testing. File upload in particular requires particular conventions to be followed with any plugin we provide. We hope that the trade off of conforming to a particular convention in order to enable fast setup with easier maintenance will be a net benefit to teams. Custom setup is always available if our design decisions are unpalatable, and we’d be happy to help you with that of course.

- Tesults Team

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

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