TestRail Reviews

We use TestRail by Gurock as a task management tool. It is integrated with Jira for task tracking.

The most valuable features of TestRail by Gurock are the user experience, it's very easy to learn. There is no learning curve needed to work on projects and manage the test cases, it is easy. Exporting and importing are simple.

The integration with Jira is very quick and powerful. If you deploy a new testing team with a full test management tool, TestRail by Gurock on the cloud will be on my top list.

TestRail by Gurock could improve by adding a defect management module tool. It would add a lot of value if I want to install it and I don't have Jira or an isolating team. For example, if I am providing a service it's separated from the development team, it then would be better to have defect management included with the test management. However, as it is now I need to be integrated with Jira or another defect management tool to complete the testing process.

In an upcoming release, they could improve the reporting module.

I have been using TestRail by Gurock for approximately three years.

The stability of TestRail by Gurock has been good.

The solution is scalable. You only need to add new licenses. I didn't face any issues. Since it is in the Cloud you add a new user to your license and it will work perfectly.

We have approximately 10 people using the solution and the number is growing.

The initial implementation took us approximately one week. We built the workflow, integration, and everything else. We optimize the process as we go.

I have a team that does the implementation of the solution.

The price of the solution is based on how many users you have per year. When you grow, it is segmented, For example, 10 to 25, you have a price, and more than 50, or 100, you need to take the enterprise license. I don't think we will reach this point.

I rate TestRail by Gurock an eight out of ten.

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. 

TestRail is basically a central repository for us since our team is geographically distributed. It is really convenient to use this on cloud. This is one use case. The other is the two-way integration with Jira. That is also one of the important factors.

We are an end user as well as a distributor.

The features that I have found most valuable are that there are various test case templates and test artifact maintenance.

Their customer support could be improved. Sometimes we struggle with that. It could be faster. Whenever we raise any query, they get back to you but the turnaround time is very slow.

Additionally, whenever there is a new version update to the cloud version, we sometimes face issues. We try to reach out to the technical team, and it requires quite a few times of trying.

In the next release, I would like to see improved technical support included. Additionally, improved backup and restore facilities would be good. At the moment, Gurock owns that regardless of whatever licenses we have purchased. That should be given to the customer.

We are using TestRail in this organization for the last two years, but I had been using it for six years previous, so it is eight plus years I have been using TestRail.

It is quite stable.

TestRail is scalable. We have scaled it from five users in the beginning to near 64 users now.

We are distributing these reports to about 100 plus people.

The initial setup is quite straightforward.

It takes hardly 10 to 15 minutes to do the initial setup.

We have only one team which maintains many tools across the organization and they take care of this solution.

We set up it by ourselves.

We are at this moment paying for a monthly payment plan.

I would surely recommend TestRail. 

On a scale of one to ten, I would give TestRail an eight.

I am a consultant. I use this solution directly and manage it. We use the on-prem model.

The most valuable features are the reporting in the dashboard and the general way in which we can create test runs is helpful.

The reporting is quite good but there is room for improvement. For example, when you define different test statuses it produces a dashboard and it creates a pie chart and it tells you what percentage is related to each test status, whether it has passed, failed, work in progress, etc. That needs to be user-definable. We should be able to customize how the reporting dashboard displays information.

For example, if I've created a new test and I want to be able to classify that data, most people aren't interested in the granular level of what the test did. They just want to know if it's a pass or fail. This could be improved. We'd like to see more customizable dashboards and analytics. 

It needs the ability to delete test results. It offers a granular level of detail but it's a pain. It needs the ability to set the results back to untested. It's a bit bizarre that it doesn't let you do that. 

It would be useful if it had its own issue management system. At the moment, it's purely a test management tool and you have to link to a defect management tool, like JIRA. It would be useful if there was an option to use its own defect management tool so that it's integrated and not two separate tools. 

Requirements and traceability would also be good additional features to be incorporated into this solution. 

I've never had stability issues. 

In terms of scalability, I don't know how well it scales because I have no view of the concurrent users. We have around 450 users on it running various different projects. Nobody has ever complained about performance issues or anything like that.

We can't easily see how many users are using it though. This is an area of improvement. We can see how many people have an account but we can't see how many are logged in and active. 

The users are mainly project managers, test managers, testers, and business SMEs.

I have never needed to contact customer support. I have posted questions on the community page. The community support is good. 

I don't have any experience setting it up on-prem. I've done it on the cloud which was very easy. It only took five or so minutes. 

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. 

I use the product to create test cases and share them with my team and manager. 

TestRail's user interface is not great. When you use it for the first time, you will be very uncomfortable and not know how to create test cases. It doesn't have a field for preconditions and post-conditions.

I have been using the product for four years. 

TestRail is stable. 

I rate the tool' scalability a six out of ten. My company has 300-500 users for the product. 

We used Zephyr before TestRail. We chose TestRail because it was already being used in other projects. 

The tool's deployment was completed in a day. 

I rate TestRail a seven out of ten. You need to have good written English proficiency to use it. 

We primarily use the solution for testing. The testing team is writing the test cases and the test switch. They were running the test for every release or every sprint because we are working on JIRA. I use the reports for the run.

The reporting is the most valuable feature. I can easily manipulate the reports into the pie charts and statistics and so on. This is very useful. Also, the ability of the solution to easily link with JIRA is helpful. It's able to integrate with JIRA in depth. 

The configuration of the software makes it very easy to use.

There are some features that I'm looking for, but I don't know if they already exist within the solution or not because I haven't had time to look further into it.

For example, if I'm interested in integration with some other automation framework, they don't have something like this, it would be ideal if they could add it. 

I've encountered at some point, some difficulties on the administration side, but I don't remember exactly what they were. 

Basically, I'm looking for more integration - especially with JIRA - and more automation. 

The solution is very stable. We've never had any issues with it.

We've never needed any technical support, so I can't evaluate it.

I didn't do the implementation myself. It was already done when I arrived at the company. I just manage the users. I switch users and accounts when someone leaves the project or joins. Being a cloud version, however, I imagine it's fairly easy to configure.

After looking at other products, I'd say TestRail is pretty expensive. It's one of the reasons we're moving away from the solution.

I played a bit with DeskLink, but I've never really evaluated it.

We were using the cloud deployment model.

I'd recommend the product. I'd rate it between eight and nine out of ten.

1. Ability to import test scenarios (CSV).
2. Redmine integration and ability to link Redmine issues to test cases.
3. Network deployment. Need accessibility world wide.
4. Report generation capability.
5. LDAP authentication.
6. Ability to control and restrict user IDs.
7. File attached upload capability.
8. Ability to note when the Blocking issue has been placed in Verify state (or Closed) and flag the Execution records for re-test.
9. Ability to note when the failing issue has been closed and move the execution record to some re-test phase.
10. Reliable and stable. It is important that TestRail be up and running 24/7 as we have users around the world using it.
11. Easy to upgrade and maintain.
12. Customer support.

TestRail has made it possible for our large team around the globe to more easily create, manage, and monitor test execution. It has also provided valuable report information used for project management.

There are a number of improvements that have been requested. While I don't have a list of these requests available, many can be found on Gurock's forum.

Four years.

No.

No.

Very good.

Previously we used a customized spreadsheet tool.

Setup was pretty straightforward. Creating our own customized reports was more complex. It required writing PHP code and they are time consuming to maintain.

Negotiate the best deal you can.

TestLodge, Klaros-TestManagement, PractiTest, Test Collab.

I would recommend researching all available products and evaluate the top three that meet your needs. There may be better products out there today. Carefully choose the tool that best meets your requirements. It is a huge investment in time and effort and very difficult to change tools once a decision has been made.

The ability to time test runs gives the tester the ability to compare calculated times to actual times it takes for a test case to run. This is the advantage over the other test management tool that we have used. Also, I liked the fact that TestRail's test cases could be linked to JIRA tickets.

Most significantly, I found it was easy to organize test cases, and that the application did not time out while I was in the middle of writing a test case.

I found it difficult to link requirements to test cases, if I remember correctly. Also, it would be nice to have a description section when creating the test scenario itself so I can indicate what the configuration should be. I was able to do this with the old tool, and I also could link requirements to test scenarios and test cases in the old tool.

I have probably used it for three months.

No.

No.

I was not the point person.

Well, I really didn't want to switch, but the rest of the team did not want to go through the exercise of learning how to configure the application for our needs.

Also, the old application was unreliable. For example, I would be in the middle of writing a test case, and before I had a chance to save the test case, I would find myself back on the previous page where test scenarios are stored. When I went back into the test scenario to continue working on the test case, all the information that I had previously entered would be lost. Thus, I would have to start all over again.

I wasn't involved in the setup. I QA'd the app, and indicated to the administrator what I desired.

I hear that the cost is a bit pricey. My advice to others is to shop around for the best deal. Some options out there are free in cyberspace.

No.

Use the product to its fullest during the trial period, and if you need an extension on your trial time, most honest companies will oblige you with an extension.