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.

Public Test Results

Share, collaborate, inform and alert like never before

blog-title-image

Why would you want your test results data to be public? We didn't think there was any good reason and that is why Tesults has never made it possible to make test results public. In fact, we've taken the opposite approach, to bolstering security and privacy with encryption at rest and in transit and even making it possible for some teams to 'bring their own encryption keys' for added security. However based on feedback it seems clear now that there is a desire for some teams to make their test results data available publicly. For example, open-source software providers have public code repositories and they also want their test results data to be public.

Tesults is rolling out a phased approach to allowing teams to choose to make data public. We will add more collaborative features and more convenient sharing mechanisms over time, but as of now you can make your test results data public should you wish to. By default all new projects will be private, you must enable public access, at three different scope levels.

Here's how to do it. First head to the configuration menu at https://www.tesults.com/config

Ensure the project for which you want to make some or all target test results data public is selected from the dropdown list. In this case the project is called Tesults.

Next click on Organization Privacy. If you have not named your organization yet, you can name it. In this case the organization is also called Tesults.

You can enable public access at the organization scope from here. If the organization privacy setting is not set to public, no matter what your project and targets are set to, the results data will not be public. Organization scope privacy supersedes project and target scopes. Next go back to the configuration menu and select Project Privacy.

Enable public at the project scope. Now go back to the configuration menu and select the target or targets you wish to make public.

Now enable public for the target for which you wish to make test results public.

At this point, with the organization, project and target scope all set to public, you can view results publicly. The URL is dependent on the name of your organization, project and target, the format is https://www.tesults.com/organization/project/target. For example, if your organization is called a, your project is called b, and your target is named c, then you would access results at https://www.tesults.com/a/b/c.

You do not need to make all of your targets public. You can choose to keep other targets private

Organization scope supersedes project scope and project scope supersedes target scope. This means that in order for results data to be public you must set all three to public. Your results will not be public if your target is set to public but your organization or project is not public.

This is the first stage to making Tesults publicly available. We are interested in your feedback and questions so please get in touch.



- 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

How AI Coding Agents Use Test Results to Verify Their Own Work
How AI Coding Agents Use Test Results to Verify Their Own Work
Why a raw pass or fail is not enough for an agent to trust its own change, and how failure intelligence closes the self-verification loop
Store and View Pytest Results Over Time
Store and View Pytest Results Over Time
Why pytest results vanish after each CI run, and how to keep a durable history you can view, compare, and track over time
How to Group and Categorize Failing Tests by Root Cause
How to Group and Categorize Failing Tests by Root Cause
When a CI run shows dozens of failures, label each one with a root cause category and group them to see how many distinct problems you actually have
How to View JUnit XML Test Results in a Dashboard
How to View JUnit XML Test Results in a Dashboard
Upload JUnit XML to a dashboard in one step, and why a test framework library gives you richer reporting with logs, screenshots, and full history
How to Keep a History of Test Results Instead of Losing Them After Each CI Run
How to Keep a History of Test Results Instead of Losing Them After Each CI Run
Why CI logs and artifacts disappear, what you lose when they do, and how to retain a durable history of every test run
How to Query Test Results With AI Agents Using MCP
How to Query Test Results With AI Agents Using MCP
How to query your CI test data failures, flaky tests and regressions with AI agents using the Model Context Protocol
ROS 2 Test Reporting with Tesults
ROS 2 Test Reporting with Tesults
Native support for the full ROS 2 testing stack — C++, Python, Rust, and beyond
Cypress Test Reporting - Beyond the Built-in Reporters
Cypress Test Reporting - Beyond the Built-in Reporters
What Cypress's built-in reporters give you and where they fall short
Playwright Test Reporting: Beyond the Built-in Reporters
Playwright Test Reporting: Beyond the Built-in Reporters
What Playwright's built-in reporters give you and where they fall short
How AI is Transforming Software Testing and Automation
How AI is Transforming Software Testing and Automation
AI is impacting software testing and automation in a big way. Here’s how AI is reshaping the testing landscape.
What is Automated Regression Testing and How to Do It
What is Automated Regression Testing and How to Do It
Learn about what automated regression testing is, how to do it, benefits, why it matters, tooling, reporting and best practices
Guide to API Automation Testing
Guide to API Automation Testing
What is api automation testing, how to do it, best practices and how to report and analyze test results