Release and Test Manager at a consultancy with 11-50 employees
Real User
Top 10
Nov 19, 2025
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.
Automation Test Engineer Il at a computer software company with 11-50 employees
Real User
Top 20
Jul 14, 2025
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.
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.
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.
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.
On a scale of one to ten, I would give TestRail by Gurock a Six. Based on my own experience, TestRail could have more capabilities. It is good to use this tool for a medium scale automation. Additionally, if you need a more automation-driven solution, I recommend going with other tools. If you just want to record, play and store the test results, if you are more in a manual testing layer, TestRail is good to use.
Quality Assurance Manager at a financial services firm with 10,001+ employees
Real User
Nov 12, 2020
I would not recommend this solution. My primary role is quality assurance. From a quality assurance perspective, there are too many limitations. There is too much integration or too many APIs that need to be written constantly. It doesn't actually give you traceability from the requirements or systems perspective. If I wanted to run automation for coverage of a system, TestRail doesn't give me that. I would rate TestRail a five out of ten.
IT Testing Manager at a tech services company with 201-500 employees
Real User
Sep 22, 2019
I would advise someone considering this solution to consider is that TestRail does not have a defect management policy. They would have to use another tool for defect management. In our case, we use JIRA, which is at an additional cost, but it's not that much. The defect management is supposed to be in a different domain because it does not fall under test management. Test case management is totally different than defect management. I believe Gurock did a great job just by separating the test management from the defect management. Good advice would be to start with a cloud for some time. I would rate TestRail a nine out of ten.
I would recommend this solution. I would use it again if given the choice. It's a straightforward tool, it's not overly sophisticated. There's not much that can go wrong with it. One small issue is the integration with JIRA. I've never gotten that to work properly for the issue management. If you're going to implement it, you're going to have to do it with an issue management tool, something like JIRA. I haven't managed to get that working in its entirety. I would rate it a seven out of ten. It is missing certain features. The integration into JIRA is not that effective and it doesn't have its own defect management tool.
TestRail helps you manage and track your software testing efforts and organize your QA department. Its intuitive web-based user interface makes it easy to create test cases, manage test runs and coordinate your entire testing process.
Easily track and follow the status of individual tests, milestones and projects with dashboards and activity reports. Get real-time insights into your testing progress and boost productivity with personalized todo lists, filters and email notifications....
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.
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.
I would rate my overall experience with TestRail an eight out of ten. Overall, TestRail provides great value and efficiency.
I rate the product a nine out of ten.
I rate TestRail a seven out of ten. You need to have good written English proficiency to use it.
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.
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.
I would rate the solution an eight out of ten. The tool is very straightforward and simple to understand.
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 would advise others to consider their enrolment needs before starting to use this solution. I would rate this solution a nine out of ten.
I rate TestRail by Gurock an eight out of ten.
I would surely recommend TestRail. On a scale of one to ten, I would give TestRail an eight.
On a scale of one to ten, I would give TestRail by Gurock a Six. Based on my own experience, TestRail could have more capabilities. It is good to use this tool for a medium scale automation. Additionally, if you need a more automation-driven solution, I recommend going with other tools. If you just want to record, play and store the test results, if you are more in a manual testing layer, TestRail is good to use.
I would not recommend this solution. My primary role is quality assurance. From a quality assurance perspective, there are too many limitations. There is too much integration or too many APIs that need to be written constantly. It doesn't actually give you traceability from the requirements or systems perspective. If I wanted to run automation for coverage of a system, TestRail doesn't give me that. I would rate TestRail a five out of ten.
I would advise someone considering this solution to consider is that TestRail does not have a defect management policy. They would have to use another tool for defect management. In our case, we use JIRA, which is at an additional cost, but it's not that much. The defect management is supposed to be in a different domain because it does not fall under test management. Test case management is totally different than defect management. I believe Gurock did a great job just by separating the test management from the defect management. Good advice would be to start with a cloud for some time. I would rate TestRail a nine out of ten.
We were using the cloud deployment model. I'd recommend the product. I'd rate it between eight and nine out of ten.
I would recommend this solution. I would use it again if given the choice. It's a straightforward tool, it's not overly sophisticated. There's not much that can go wrong with it. One small issue is the integration with JIRA. I've never gotten that to work properly for the issue management. If you're going to implement it, you're going to have to do it with an issue management tool, something like JIRA. I haven't managed to get that working in its entirety. I would rate it a seven out of ten. It is missing certain features. The integration into JIRA is not that effective and it doesn't have its own defect management tool.