Skip to main content

What We Recently Released?

In February, we released 2025.1 to our SaaS customers which features several performance improvements, addresses multiple bugs, enhancements to qTest Copilot, and includes a new capability – the ability for administrators to block users from uploading executable files. This new feature has been an ask of our customers and to ensure qTest can comply with your internal security policies, you can now ensure potentially risky files are not hosted in your qTest instance.

 

What’s Next?

We’re gearing up for the 2025.2 release for both SaaS and on-prem customers. We’re tracking for April with this release and can’t wait to get these updates in the hands of our customers! With 2025.2, we’re releasing the first of several planned improvements to Insights.

For 2025.2, we plan to deliver enhancements that include:

  • A revamped Insights homepage to improve the navigation process
  • The introduction of pre-calculation to significantly increase the speed with which reporting loads --- we will start with the Test Runs and Test Cases reports in Explore Data
  • Performance improvements when using “site fields” in reporting

As we look ahead to Q2 and our 2025.3 and 2025.4 releases, our priorities will be:

  • Continued performance improvements to Insights, including additional Explore Data reports and dashboards
  • Enhancing visibility of Tosca automations in qTest to reduce the need to switch back and forth between the tools
  • Tactical improvements to our Jira integration and investments in our SaaS platform for scale and performance

For qTest Copilot, we’ve been getting great feedback from customers and are continuing to tweak our test case generation capabilities. We plan to add additional capabilities, such as creating test cases from screenshots and attachments, to better accommodate how our customers create their requirements.

We’ll share more on our progress on these initiatives in our next update!

 

Looking Ahead

Later, we have plans to focus on:

  •  Enhancing our cross-product reporting capabilities, specifically between qTest and Tosca, enabling users to get better insights into their test coverage
  • -Investments in our APIs, specifically with a goal to improve performance and scalability
  • Deeper Tricentis platform integrations, specifically with our Quality Intelligence solution, SeaLights

As always, we’d love to hear from you and your feedback on where else we can improve qTest to help you drive higher quality and, as always, thank you for your trust in qTest and Tricentis as key partners in your quality operations!

 

I love qTest!!  But I’m seeing it be replaced in companies I’ve worked for.  The 3 main reasons:

 

1 - with Jira Cloud, you can’t see the test case names in the Jira ticket.  You only get the test case ID.  You also can’t see the test run results anymore

2 - When creating test runs with parameters, you get the test case name with numbers after it.  What people want is to see the parameter name instead of a number.  So then I can select all cases that deal with Firefox and run them together

3 - In the test case folder, cases with long names are hard to see since you have to keep scrolling back and forth to find the test case name.  Let the name wrap around in the tree so you can see it all instead

 

Fix these 3 things, and you’ll lose less customers.


Hi, thanks for leaving this feedback and I truly appreciate the detail. I’d love to speak with you to learn more about these specific capabilities and to pick your brain on how else we can best improve qTest. Please feel free to reach out to a.patel@tricentis.com at any time if you’d be open to a conversation!

 

I love qTest!!  But I’m seeing it be replaced in companies I’ve worked for.  The 3 main reasons:

 

1 - with Jira Cloud, you can’t see the test case names in the Jira ticket.  You only get the test case ID.  You also can’t see the test run results anymore

2 - When creating test runs with parameters, you get the test case name with numbers after it.  What people want is to see the parameter name instead of a number.  So then I can select all cases that deal with Firefox and run them together

3 - In the test case folder, cases with long names are hard to see since you have to keep scrolling back and forth to find the test case name.  Let the name wrap around in the tree so you can see it all instead

 

Fix these 3 things, and you’ll lose less customers.