TestRail Reviews

I'm running an agile release train and we use TestRail for agile testing, mostly for manual testing, to keep track of test statuses. We link it directly to our user stories and execute our test cases, and because it has integration with Jira, we can see the test results appearing in our user story.

We create the test cases in TestRail based on our acceptance criteria in the user stories, and then execute them in TestRail and link the Test Runs to our user stories. 

We manage our test cases in TestRail and our test repository is in TestRail for regression testing as well.

It's quick and easy with a very low learning curve. What I also like is that it has different types of formats for test cases. You could easily use traditional test cases which are step-by-step format, or you can use a BDD format, for example, or you can just use a very simple format. It's very easy to use and simple with a low level of complexity. There are pros and cons with complex tools, but the advantage of TestRail is that it fits in really well with an agile life cycle. If you're working agile, it is quick and easy and simple to use. Just the bare minimum is all you need for agile testing.

The integration with Jira is good. I like that because it helps to show your test results and helps you to keep traceability between your user stories and your test results.

The analytics and reporting capabilities in TestRail are not very extensive and tailorable. This doesn't make it very suitable for enterprise level programs. With OpenText, you have a lot of flexibility. I'm talking about the old version of ALM, the desktop client, which I used when it was still Micro Focus ALM. It has a tremendous ability to generate different types of reports. You can build different graphs, have Word document format, Excel format, or write your own Excel queries and incorporate that into your own reporting. 

TestRail has one type of format. If you want to generate a test summary report, there is basically only one format that you can use. You can't add your own components. You can choose which portions of your test results you want to include by selecting certain sections, but you don't have freedom to add and remove sections yourself. It's predefined and all that you can do is just take out the ones that you don't want. It is usable, but it's not tailorable, it's not configurable, it just gives you the bare minimum.

It depends on what you use the tool for. If you want to use TestRail for enterprise-level waterfall projects with traditional reporting and a lot of analytics, it's not good enough because the analytics, dashboards, and reporting are not really there. However, if you use it for agile and you want quick and easy with very simple functionality, then it's very good because it's simple to use. For agile use cases, it's great and you don't need more than that. But if you are looking for an enterprise tool or waterfall project with large programs, even the enterprise version is not sufficient. There's no significant difference from the basic version. The only thing that you really get is the ability to have multiple project reporting, but the reporting itself is limited. There are no configurable dashboards. You can report across multiple projects, which is great, but the type of reports that you can run are limited to the current set of built-in reports. That's not good enough for enterprise level with multiple project and large programs. You want multiple reports across multiple projects and you want the tailorability and configurability of having dashboards and analytics, which TestRail is weak on for the enterprise level.

About two years.

I would say seven or an eight because sometimes there are hiccups in the interface with Jira, for example. I think an eight is fair.

Usability is a concern. The user interface can be improved in terms of navigation and searching. When you do test runs, you can have pages and pages of test runs. When you want to search, it's difficult to search because there's too much data and the navigation around the search functionality can definitely be improved. Sometimes it doesn't find data even if you know that it is there.  TestRail doesn't allow you to organize test runs to me more manageable. It also doesn't have the analytics and dashboards that you need for large scale enterprise implementations, which is why it's not really scalable.

With regards to customer service and support, it depends on whether you're talking about the vendor directly. Our support goes through various layers - internal to the company, then with the vendor who supports the product in our country and then with Gurock. So that makes it difficult to evaluate the level of support. In general it is not too bad, and because we are a big company we tend to get a lot of focus. I do also think Gurock is committed to the product and constantly trying to improve, which is a good thing.

Positive

Complex dashboards are not important for us in because we don't use them in the Agile space. What we want to track in Agile is to see that when you do a test run, it has the graphical result of the test run, or if you do the milestone, it has a graphical result of the milestone and that is pulled into Jira. When you do a release, you can link that milestone to the release and you have one graph to show you pass or fail, and that's all that we need. For our purposes, that's more than enough. We don't need complex dashboards or have to build them, and they're not available in any case. But we don't need them for the agile approach that we use. The review rating for TestRail is eight out of ten.

I used to work with Selenium at the start of my career, but right now, from the last almost four and a half years, I'm working on Leapwork automation tool.

For automation, I used to work on different tools such as JMeter and Selenium, but when I joined Tyler Technologies, USA, we were trained for using Leapwork, and when I use it, I simply love Leapwork. As far as the other tools, we use other tools for management purposes, such as TestRail, Jira, and other software. For automation purposes, we mainly work on Leapwork to automate our processes and scripts.

Basically, we follow the CI/CD testing environment, continuous integration, and continuous development. What we do is there is a product, ABC product, and we receive a request from a client to add a feature in this product. Before adding that feature, we have data and reports from the past that show the behavior of our product, the current bugs, and the number of test cases which got passed or failed. Then we integrate and add the feature which the client requested. After adding the feature, we simply run all test cases again, including the previous ones which we had before adding the feature. Then to test the new feature, we write new test cases, create automation flows, run them, and then run the whole regression run of flows to test the new feature.

TestRail is a tool where we have test cases for our ABC product. Test cases mean there is one module in the product, for example, the payment module. To test that module and verify if it is working properly, we write steps. We use TestRail to write these steps. In TestRail, we have options in which we can write the step-by-step process of each test. We can write one single test in multiple steps to make it more understandable.

TestRail has many great features. We can use attachments with it, such as videos or screenshots for proof or for any new user who is not familiar with the product. The steps can be edited by anyone and we can see the history as well, including who has edited or modified the test steps. The reporting capabilities and the simplicity of it make it user-friendly, as new users can easily understand the tool. The simplicity would be the greatest benefit of TestRail.

I have integrated TestRail, Leapwork, and Jira together using PowerShell scripting. When we have 100 test cases and before every release goes out to our customers, we kick off the regression run in Leapwork. At runtime, when the test case passes, it reflects the results on TestRail. If it fails, it automatically creates a Jira story and sends that story to our backlog for further investigation to determine if it's a product issue, Leapwork tool issue, or a logic issue in the automation scripting.

In TestRail, there is significant difficulty with roles and rights. They are not in the mainstream. The person who has the license has all the rights, which is understandable, but TestRail needs to make it more clear and visible by dividing into segments. For example, distinguishing between a user, modifier, or author, and giving them badges or positions to indicate their capabilities. Any user must know their capabilities while using TestRail and what they are able to do.

When I started automation testing in my current company, we only had 10-20 automated test cases integrated with TestRail, but we scaled up to thousands. We managed this scaling without any major issues. For other companies and people, TestRail can be used effectively because there is a great community available on Google.

I used to work with Selenium at the start of my career, but for the last four and a half years, I have been working with the Leapwork automation tool.

Sometimes we encounter issues with TestRail, but that's very rare, occurring once in six months or so. When TestRail goes down or becomes unresponsive, we inform our IT department and they coordinate with the TestRail team. These issues are usually resolved quickly.

TestRail is definitely scalable. When I started automation testing in my current company, we only had 10-20 automated test cases integrated with TestRail, but we gradually increased to 100, 200, 1000, and 2000 cases. We achieved this scaling without any significant issues. Other companies and people can use it effectively because there is a great TestRail community available on Google.

My team who manages licensing and administrative tasks, including HR people and IT people, escalate their queries to the TestRail team, and most issues were resolved. I personally escalate Leapwork issues with the Leapwork support tech team, and they are very quick to solve problems.

Positive

In the old school way, people used to write test steps in Excel sheets. I also used to do that, but that was not an effective approach. I haven't used many test management tools. TestRail has been the primary tool I have used in my career.

I was involved in the initial setup after discussions with my manager, team, and management decided to implement TestRail. After receiving credentials and sorting out licensing, I started using it and provided feedback week by week, month by month, year by year. We have built a great system using TestRail.

I was the first one hired and given the responsibility to create the whole framework and build the system for automatic testing to save time for manual testers. I started building the system gradually, hired and trained multiple people. We follow scrum methodology with daily stand-ups and meetings to share progress. I conducted proper training sessions about our framework, integration, and the purposes of TestRail and Jira. I created a demo system for them to practice and learn, and they can always ask questions when needed.

I used to work as a manual tester before moving completely to automation. After running 100 flows for multiple releases, we receive an automated email showing the results. If 15 test cases fail, we investigate the reasons for each failure. The investigation process involves checking reports and logic to determine causes such as site downtime, unstable environment, or missing scripting logic. These investigations need to be done manually, and I have trained my team members to follow this process.

TestRail is a tool where we have test cases for products. For example, with a payment module, to test if it's working properly, we write step-by-step instructions and record the results. In TestRail, we can write detailed steps to make tests more understandable. To automate, we mimic these steps in Leapwork. This saves time and effort as we can run tests whenever needed.

I would recommend examining what people are building and their product requirements, but TestRail has proven to be the best fit in most environments. After seeing specific details, I would be happy to share my thoughts about TestRail.

Tyler Technologies should be mentioned as a reference.

This review rates TestRail at 7.5 out of 10.

My main use case for TestRail is test case management and release test execution tracking. It is mainly used to organize test cases, run regression cycles, monitor progress, and provide clear visibility of testing status before production releases.

The best features of TestRail for me are centered around organized test management, execution visibility, and reporting. It is a practical tool because it helps manage the complete QA cycles in one place.

The best feature is Test Case Management, which is the feature I use the most. It allows teams to create, organize, categorize, and maintain reusable test cases in structured suites and subsections. It makes regression cycles much easier.

Second is Test Runs and Execution Tracking. We can quickly create release-specific test runs, assign cases to testers, and track real-time status such as passed, failed, blocked, or retest.

TestRail has had a strong positive impact on the organization, mainly by improving test management efficiency, release visibility, and overall QA coordination. First is time saved in test cycle management. Before using a centralized tool, many teams rely on spreadsheets or emails for tracking. With TestRail, creating test runs, assigning cases, and monitoring status become much faster. In practical terms, I would estimate around 30 to 40% reduction in administrative effort during regression cycles.

Faster release readiness decision is the second point. Real-time dashboards showing pass-fail rates, blocking cases, and pending execution help management make quicker go/no-go decisions for releases. This reduces delays caused by manual status consolidation.

Improved team productivity is another key benefit. Testers spend less time maintaining trackers and more time on actual testing, defect validation, and exploratory testing.

TestRail is a strong tool overall, but there are several areas where it could be better. The first area is user interface modernization. Some parts of the interface can feel dated or less intuitive, especially for new users.

The second area is faster performance on large projects. In environments with large test repositories, many users, or heavy historical data, navigation and report loading can sometimes be slower than ideal.

I have been familiar with TestRail for around two to three years. During this time, I have used it primarily for test case management, planning regression cycles, tracking execution progress, coordinating with QA teams, and generating test reports for releases.

My advice would be to first evaluate your test process maturity and team needs. TestRail delivers the most value when you need structured test case management, regression planning, execution visibility, and reporting across multiple releases or teams. Start with a clean test case structure, naming standards, priorities, and ownership model. Also, plan integrations early, especially with Jira or your DevOps tool. If implemented properly, it can significantly improve QA discipline and release quality. I would rate this product an 8 out of 10.

Neutral

We use the solution for test management during projects.

The solution helps us with the general management of projects. It provides us with visibility on progress and quality.

The most valuable feature of the solution is that it's an excellent repository for TestRail suite. TestRail provides effective test management and test execution, along with real-time reporting capabilities.

I have faced some issues with the integration between TestRail and Jira where the status of tests is not displayed (in Jira) due to I suspect security settings on the browser. In a large corporate environment, it is not easily changed. The support wasn't particularly helpful.

It would be great if I could create custom reports, ideally with a tool designed specifically for that.

I have been using TestRail for seven years. I have used the cloud version of the product, which is the latest, and I have also used the on-premises version.

I haven't faced any stability issues using the solution. Stability-wise, I rate the solution a ten out of ten.

I haven't faced any scalability issues using the solution. Scalability-wise, I rate the solution a ten out of ten.

My company has got a license for two hundred people who use the solution.

The solution's technical support hasn't resolved one or two of my problems. In general, the solution's technical support is pretty good. The solution's technical support team couldn't resolve some compatibility issues I was facing.

I rate the technical support a seven out of ten.

Neutral

I have used Zephyr and ALM in the past.

The installation of TestRail is not required in its cloud version. With the on-premises version of TestRail, the installation process is straightforward. I did not face any major challenges with the installation part of the product.

The solution's deployment process takes a few hours because of the required configuration, implementation, and testing.

The solution is deployed on TestRail Cloud, which is a public cloud since it's available for anyone to sign up. It is essentially a SaaS product.

One of the current clients that I deal with is an insurance client, and from an audit perspective, capturing all of the test evidence and test results in a tool provides a detailed level of audit capability required by the user, making it a useful product. TestRail makes the whole test management process more efficient, though measuring its efficiency is a bit more difficult. It provides financial benefits to its users.

The solution is quite reasonably priced for what it offers and offers a monthly subscription model.

I don't own an actual technical support contract with Gurrock so I don't know what terms have been agreed. However, the cloud version is reasonably priced and can be scaled easily. The on-premise version obviously has an additional cost associated with standing up the infrastructure, support teams, OS/DB licensing costs, etc. It is also worth bearing in mind the overhead for upgrades and associated testing.

My advice, go cloud.

IT governance for security patching and operating systems are areas where the maintenance for the solution comes into the picture. Patching is done automatically on the cloud version of the solution, while patching has to be done manually for the on-premises version. There is a combination of application patches, and then there are operating system patches as well.

One or two engineers from the IT department are involved in the solution's maintenance process.

I recommend the product to those planning to use it.

I rate the overall product a nine out of ten.

We use the product for test management. We use it to create test cases and milestones and to record the results.

We use the solution for testing purposes. It efficiently creates test cases and milestones and records the results. It saves us a lot of time.

The product helps us create test cases and reports. It also helps us in milestone tracking.

The product has to improve reporting. The reports should be more user-friendly. The solution should provide data at a user level while tracking milestones. The reporting is slow. It takes time to get the data sometimes. The performance of the tool should be improved.

I have been using the solution for four years.

I rate the tool’s stability a nine out of ten. I am satisfied with the stability.

We face some performance-related issues as our data grows. I rate the scalability an eight out of ten. Approximately 100 people in my organization use the product. Our employees work in different time zones. We use the tool five days a week. We rarely use the solution on weekends. We do not have any plans to increase the number of users.

The technical support must be improved. There is a lot of to and fro before our issues get resolved.

Neutral

Compared to other tools, I rate the ease of setup a seven out of ten.

Since it is a cloud-based product, the vendor did the deployment. The vendor also does the maintenance of the solution.

The product is not much expensive. I rate the pricing a four or five out of ten. There are no additional costs associated with the tool.

My organization has been using the solution for seven years. The solution is deployed on the cloud. We are using the latest version of the product. Overall, I rate the solution an eight out of ten.

We use the solution for test management and reporting.

The integration with Jira and the ability for extra configurations are the most valuable features.

The test suite management has room for improvement as well as better reporting.

I would like the availability of some APIs included in a future release of the solution so I can extract test execution status and build my own custom reports rather than relying on exports.

I have been using the solution for six years.

I rarely have any issues with stability, I shall go with a solid ten out of ten.

This is difficult to gauge but I rarely have any performance issues with it so I won't over-commit and give it a seven out of ten.

We have around 200 users.

The technical support is quick to respond but they did not provide a resolution for my issue.

Neutral

The initial setup is straightforward.

I give the price a five out of ten. The price is midrange.

I give the solution an eight out of ten.

I recommend the solution to others. Being cloud-based the solution is easy to deploy and integrates well with Jira.

I use the solution for test management. 

TestRail should improve its pricing. 

I have been working with the product for four to five years. 

TestRail is stable. 

My company has two to three users. 

TestRail's deployment was easy. 

I rate the product a nine out of ten. 

I was on the lookout for automation testing on the browser and I believe this tool is very interesting in that matter. The solution is useful for UI testing. You just need to add the URL that is to be checked. 

The product is not focused on synthetic data creation. I would also like to see more integrations with other platforms. 

I have been working with the tool for a couple of months. 

The solution is stable. 

I am the sole user of the tool. 

I used only online materials and online support. I never contacted the tech team directly. 

The product's setup is straightforward. The tool's setup takes only a couple of minutes to complete. You need to look through the training material and follow it. 

There is no technical team needed to do the solution's installation. 

I would rate the solution an eight out of ten. The tool is very straightforward and simple to understand. 

I am responsible for the administration of this solution including onboarding, permission levels and daily project management. We have 2000 plus people using it.

This is a user friendly solution. 

This solution has room for improvement. For example, some particular projects need to adjust access or add additional members and this isn't always possible. Role-based access would improve this.

The future projects, we would like to be able to assign roles to the lead to enable them to complete customization, add users and add groups. 

I have been using this solution for two years. 

We have not needed to contact the technical support team.

Our company decided to use TestRail by Gurock as a trial to monitor the dashboards for projects.

The initial setup is straightforward but customization can be complicated. 

I would advise others to consider their enrolment needs before starting to use this solution. 

I would rate this solution a nine out of ten.