Last fall, we launched our first Testmo User Survey, gathering insights from users in 73 countries, representing over 1,000 companies across 100 industries. They shared key challenges in testing and development for 2024, along with their improvement goals for 2025.
Over the winter, our team combed through and reviewed the feedback to shape our 2025 roadmap (more on that below!). Here are ten key insights we gained.
One of the questions we asked Testmo users was which tools they used to define requirements, track defects, and run their CI/CD pipelines. This was important for us to understand because effective test management requires being able to integrate seamlessly with your team’s existing tech stack (which is part of why we designed Testmo to support 15+ issue trackers and all of the major CI/CD platforms out of the box).
Needless to say, we weren’t surprised to see Jira so widely used. That said, we were slightly surprised to see Jenkins continue to be so highly-represented amongst the CI platforms, given the widespread adoption of GitLab CI and GitHub Actions across the industry. Though we don’t anticipate Jenkins will ever go away completely, we’re anticipating GitLab CI and GitHub Actions continue to increase in adoption over the next year or more given how easy GitLab and GitHub have made it for teams using their source code solutions to integrate with their respective, platform-native CI offerings.
Similarly, we were not surprised to users report a high level of test automation adoption. Nearly 85% of respondents reported using some test automation as part of their test strategy, with 25% respondents saying test automation actually accounted for more than half of their testing activities.
There were clearly some test automation frameworks and tools were more widely employed others, with more respondents reporting using Playwright, Selenium, and Cypress than many other common tools and frameworks. One on hand, it’s not surprising to see these three platforms higher than others, given that web UI / frontend automation testing is typically one of the more common use cases for test automation frameworks. That said, it was interesting to see Playwright continue to rise in popularity since only being released by Microsoft in January 2020.
Like many other professions and industries, many software testing and QA professionals started to discover some of the real use cases they had for using commercially-available AI tools. Of the 500 or so Testmo users who responded to this year’s survey, nearly a quarter of them responded that they started using AI in their software QA practices, at least at some level, in 2024.
Unsurprisingly, almost 60% of the individuals who told us they started to adopt artificial intelligence in their QA processes said they were using it to generate test cases or scenarios. While tools like OpenAI’s ChatGPT and Google’s Gemini aren’t anywhere near perfect, many QA teams have found that they can be helpful to write the first draft of a test case, help brainstorm alternative scenarios to test, or iterate through various sets of combinations of test data.
Once you have generated some ideas for test cases using AI, you can use a test management tool like Testmo to save the cases in your test case repository, add metadata or custom fields, and request a review from another member of your team.
It’s important to remember to check any output provided by AI tools before using it in your production environment to eliminate any potential errors from hallucinations or inaccurate information and make sure the data is actually relevant for your use case.
Besides the negative environmental impacts of AI highlighted by groups like the UN Ecological Programme, one of the most significant concerns that various sources have highlighted around the use of AI are around data privacy and security. More than 40% of Testmo users who have started implementing AI named this as their biggest challenge.
In addition, many teams struggled implementing AI in a meaningful way because of a lack of expertise in the team or AI tools that actually made a difference in testing.
While the majority of Testmo users reported using some form of agile development processes, we were impressed to see that more than 55% of our customers reported deploying new updates or versions at least once a week.
Many users added notes that they might release to development or test environments multiple times a day, but only deploy to production once a week or a few times per month. Still, the overall feedback we received clearly demonstrates the way development teams continue to focus on shortening release cycles and increasing both frequency and speed of deployments. For testing teams, that means having to work even harder to automate as much testing as they reliably can, rely on techniques like exploratory or user acceptance testing, and generally work even more efficiently than before to keep pace.
When we asked Testmo users about their top challenges around testing & QA, automating more tests was far and away the most prominent answer.
However, the issue here clearly isn’t just a technical one. If you take a closer look at the second- and third-place answers, it quickly becomes clear that the root of issues faced by testing & QA teams right now comes down to resourcing. Without enough team members dedicated to QA, teams don’t have enough time to appropriately evaluate the quality of new releases and mitigate potential issues.
Unsurprisingly, our users reported that automating more tests was also their top objective for 2025. Taking a look at the other top objectives they identified, it’s clear that QA teams are largely being tasked with the same core responsibility that they have always had: to find ways to increase test coverage (for example, by shifting more checks to automation) while continuing to speed up the process of testing (e.g. by making testing more efficient and building better processes around QA).
Ultimately, it appears the main outcome QA teams are measured by remains largely unchanged: improving the reliability of QA in order to reduce bugs that slip to production. And despite the widespread discourse in the QA community about QA’s shifting role in helping the “whole organization” adopt a quality-first mindset, it doesn’t appear that this objective bubbled to the top of most teams’ priority lists in 2024. This highlights an area of significant opportunity as we continue through 2025.
When we launched Testmo, we set out to create the fastest, most productive, user-friendly test management platform on the market. We knew it was important for QA and development teams to be able to integrate with their existing tools like Jira, GitHub, GitLab, etc., see all their test activities at a glance, and speed up the process of testing itself.
Needless to say, we were very excited to see many of these goals reflected positively the comments our users provided when asked to name their favorite parts of Testmo.
One area we specifically focused on as we designed Testmo was making sure the user interface was fast, responsive, and easy to use. We were very excited to hear so much feedback from so many users that we, by and large, achieved our goal! Here’s what some users had to say:
Given how important test automation is to the success of modern QA and testing teams, we also built Testmo with test automation at the core of the application. Testmo works with any test automation tool and framework to report your test results for test automation management. And it works with any workflow, whether you use CI/CD pipelines, a build server, or manually launch your automated tests.
In a similar vein, we were very excited to hear so many users reflect back that our test automation integrations are one of the main features of Testmo that they liked:
We know that not every team uses the same testing process, and that even different teams at the same company can have drastically different workflows depending on the product, platform, or module they are testing. For that reason, we built Testmo to be as flexible and customizable as possible, which is an area where we will continue to improve in future releases. Here’s what users had to say:
Of course, test automation isn’t the only type of integration that our users need to ensure Testmo helps them and their teams be productive as possible. Testmo is designed to integrate with many popular tools so that you can do things like link your test artifacts with user stories, requirements, bugs, or other issues logged in your team’s issue-tracking tool, integrate Testmo with your CI/CD pipelines, and log in with third-party authentication providers. Here’s what some of our users had to say about what they liked about Testmo’s integrations:
Finally, beyond simply providing users with a more productive way to track testing, one of the most important features of a test management platform is the ability to see the status of your test cycles updated in real time. Testmo gives QA teams a way to track all your testing efforts in a single place with live status, activity, progress and key performance metrics, as well as flexible, filterable PDF-reporting for easy sharing outside of Testmo. Here’s what some users had to say about what they liked Testmo’s reporting features:
While everyone likes to hear what they are doing well, it was actually most valuable to us to hear about the areas we can improve. As we read users’ answers about the areas they wanted to see improvements in the product, these five themes stood out:
While we had already received feedback, feature requests, and other ideas for improvements before the survey itself, it was incredibly valuable to be able to read everyone’s feedback in the survey at once, and played a significant role in helping us nail down some of the priorities for the year ahead. Without further ado, here’s a sneak peak of where we’ve landed for our 2025 roadmap plans (though all of this is subject to change at some level based on ongoing customer feedback and input, of course!).
We are very excited to share that we will soon be releasing our newest feature to Testmo: the Testmo Reporting Center. The Testmo Reporting Center will provide QA teams with the ability to generate live, configurable reports based on various options, settings, and the scope defined for each specific report. It goes beyond Testmo’s existing PDF and CSV exports available in many other areas of Testmo to provide additional insights, metrics, and summaries of data that currently aren’t as easy to generate in a single report.
You can expect to hear more about the launch of the Testmo Reporting Center in the coming weeks as we begin to roll out the preview release to all users. We plan to introduce the Issue Coverage & Traceability report first, followed by additional reports around Milestones, Test Automation, and Workload throughout the rest of this quarter.
As excited as we are to get the Testmo Reporting Center into users’ hands, we’re just as thrilled about the rest of the product improvements and new features we have slated for later this year. Here’s a quick overview of some of those projects we’ve identified:
That said, we actively welcome any and all feedback at any time of the year! Have an idea for an improvement you’d like to see, or a feature that would drastically improve your team’s ability to be efficient and productive? Drop us an email at [email protected] any time and we’ll log your request for future consideration!
As a final note, we just want to say a final and heartfelt thank you to all of the Testmo users who took the time to participate in last year’s user survey, and give a special shout-out to the folks who won one of the 20 digital gift cards we distributed at random to survey participants, including Sophie, Courtney, Nikki, Daniel, Ferit, Mary Kate, Molly, Ami, Johny, Jacob, Fabian, Emanuel, Alex, and the seven others folks who didn’t wish for us to publish their first names. Serving you and your teams is the reason we do everything we do, and we look forward to continuing to working with you for many years to come!
