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.

No case pricing

Number of cases no longer a consideration for pricing

blog-title-image

We are excited to announce that the number of cases per test run is no longer a consideration for pricing. To make this possible Tesults has undergone a massive back-end restructuring to completely change the way we process and store results data.

With the previous system architecture it simply wasn’t possible to take cases out of consideration but it was never something we were happy with. Software development teams should not need to think about how many test cases they have in a single test run for reporting. In addition, it made keeping the Tesults mission around consolidating results from several source targets difficult to achieve for projects with higher numbers of test cases.

While our team was busy implementing this change we decided to do other awesome things too:

  • Rate Limits: Previously the rate limiting applied at 5 results api calls per 15 minute period. From now on all new plans reduce this period to only 5 minutes.
  • Data: We offer far more data now per target than was previously provided by default. You can still increase this manually but we suggest leaving it at the minimum amount unless Tesults shows you are reaching plan limits on the results page.
  • Case Limits: As mentioned, you no longer have to decide on the maximum number of test cases you will be uploading on each test run. There is a default cap in place of 10,000 but we are happy to increase this if you get in contact with us and ask for an increase.
  • Simpler pricing: default pricing (applied if you do not change data settings) makes pricing so much simpler. From now on all new plans charge $25 per target. That’s it! All you really have to think about now is how many targets your project and team needs. This target price includes 25 team members and 30 days history. Each additional 25 team members is only $5 extra per target. These prices are for a monthly rate if paying annually. Check out the new pricing page for more details.

Existing customers will remain on their existing plans unless they choose to change to new plans based on the new pricing. Changing is easy to do from the configuration menu and you can change plans at any time. We will be sending emails to project owners and officers to make them aware of the pricing change. Take a look at the new pricing page and if you would incur a higher charge we suggest you remain on your current plan. For customers who would make significant savings you can either take advantage of these savings or you can get far greater value from Tesults by getting more targets at the same rate.

We are super excited with this change, it makes us happy that teams no longer have to think about how many test cases they have when using Tesults and we think this makes Tesults far better positioned to offer massive value with respect to results consolidation from several targets.


- 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