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.

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.

We mainly use TestRail for test management activities, like creating a test case, logging a defect, assigning to a user story, exporting the test cases, and generating reports.

Since we are using Jira, a project management tool, TestRail comes as a plugin for it. So as soon as the user stories are written there, we can integrate TestRail just like a test case and we can link the test cases to the user story easily and make requirement traceability metrics. I have an automation test kit, as well, and I can call it from TestRail. It is a centralized solution for whoever is working in a project. They are able to see which user story is tagged and to which test case and what the result is. Do we have anyone? How many test cases were written for a particular user story? What is the status on that one? This can all be tracked easily.

The feature that I have found most valuable is the dashboard.

TestRail clearly provides the team members productivity. For example, if I select a particular team member, I can see how many test cases he developed or executed and at what point of time. Additionally, is the defect aspect. In which area is the defect in? Suppose I come up with a lot of filter attacks on some modules. If I filter by that, I am able to create defects easily in the TestRail, I can export it into reports, and present it to all the stakeholders so that they can easily understand the status of the delivery, exactly where the defects are, and where the progress is. The report process is very nice to go along with the test management.

With TestRail, the APIs are there, but they may not be able to easily integrate with the Jenkins.

I think it's not directly integrated with automation kit solutions. Maybe manual test cases have APIs, but they may not be with automation specifics. Suppose I have a Selenium automation and I want to run it from a TestRail. Obviously the TestRail should have an agent for it, an automation server should be configured, but I don't think they have this.

I have been working with TestRail for one and a half years.

It is stable. I don't think there are any gaps in there. It is working fine as it is.

Their scalability is okay. We have a small QA group and we started with 50 users and scaled its use to 150.

I think maybe two people would be enough for maintenance.

I don't think the initial setup is complex. It is just a Cloud-based system. We need to access the URL and we need to do a single sign-up for it. Since it's an organizational level, we want to maintain security and we need to test identification through a browser and enable the employee profile in the Cloud. That's it.

When we did the initial level POC, we did it on Cloud for the pre-trial version. But since our organization is a healthcare level, we took TestRail and configured it for our own use On-Premise.

There are a lot of Okta authentication there. It is a two-factor authentication. So, the moment when we are associated with that kind of app, it connects to the TestRail wherever they're hosting a server. It is kind of an exchange of data through the Okta app for security authentication.

It depends on the number of users. I think our price is something like $300 to $400 a year.

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. 

We use it for test case repository and test management. My primary role is quality assurance. I've got one developer who looks at the SQL, upgrades, and a few other things. I do the customization, integration, and normal administration for granting access. I also provide user support and help users with training, guidance, demos, etc. I handle 80% work, and the developer handles the remaining 20% of work on this solution.

From a testing perspective, the management is awesome. I am able to do testing and then add the reporting and the evidence.

It is fair in terms of the price that you're paying. You get what you're paying for.

I do see room for lots of improvement in it. In terms of usability, duplication with test cases and constant creation of projects isn't easy. There is also too much API integration into automation tools, which is not there in ALM with UFT.

Instead of setting it up as a project and using it, we set it up as a system for usability. It also lacks in the traceability aspect. For traceability, you need to use the JIRA plugin and drag traceability on JIRA, but the functionality is still quite limited.

The biggest gap is mainframe testing. It would be good if I could start with mainframe testing. Manual granting of access is another issue. There is no API that I could use with another system where it is automated. There is an API for loading somebody to a project but not for adding to the application.

I have been using TestRail for two years.

I have not contacted technical support.

I learned to work with this solution, but if I had to choose a solution, it wouldn't be TestRail.
I also use ALM, and it is my preferred tool. Tosca also has the same quality level as ALM.

Its price is definitely not more. If they introduce automation, they can charge more.

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 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 use the on-premises deployment model of this solution. Our primary use case is for test management. 

It was very easy to create a quick test plan, despite the challenges we face, like a lack of documentation and the lesser knowledge we have for testing. We were testing a new upgrade for an app and by just exploring and running things through our mobile app we found that many features that were existing already in the production environment in the production app were not documented properly. All we had to do was create an exploratory session with the feature that we have to test and then we created a test plan with a different composition like Android and the languages that were working. 

It took me less than an hour to figure out the test plan and the test execution was more managed in the sense that we did have a test case at this instance to be executed. The stated test results are not easily monitored when it's reported. Before we used to have a more complex system and we used to manage the test cases in Excel format, so we saved a lot of time with this. 

In the next release, I would like to see dynamic reporting. 

The most valuable features are the flexibility, ease of use for writing new test cases, the test plans, and the composition.

It's not easy to create a custom report. It's not straightforward. A good improvement would be if there was a way to report and create a custom report without using a plugin or scripting language.

It's very stable. 

We use it on a medium scale. We have 100 users licensed but have around less than 50 active users. I haven't seen any performance issues. I haven't seen any issues with scalability. It's very stable and nice.

I handle the maintenance. I have handled it now for the past three months and nothing happened. I haven't had any need for maintenance yet. One team member can handle the whole thing.

In terms of our plans to increase our usage, in another six months, we were planning to ramp up the team, but I don't think it will have an effect on this solution. 

We previously used HP Quality Center for the last eight years. We switched to TestRail because it is more flexible and cost-effective. The price is very competitive, and even though HP is the ultimate solution, for a starter company or like in our case, the cost was a major factor. 

The initial setup was kind of complex, but I have previous experience that helped. It was not really straightforward. I heard that with the new version, it's in a package and it's not so complex anymore. 

The deployment took around two days. I did the deployment alone and wasn't doing it full time. I did the PoC first and then purchased the license. 

We purchased a license for two years. The license is on an annual basis. We got a nice discount for the second year, around 10%, which is nice. It's priced annually and per user. It's a fee-based license. One thing that Gurock does not offer is a perpetual license. There is no option to buy the tool without having to make a recurring cost. It is fine for us. The annual license is not an issue.

We also looked at TestLink in open source, and we looked at ALM. The functionality and the usage, and usability of TestRail is much better than any other product. It's not dependent on any ActiveX or any library. The client can use it out of the box, they just need to type in the URL and start using it. Also, the training videos are very nice. It covers everything, that would be all you have to do is just watch the videos for a few minutes and you can really just learn very quickly and easily. Other tools, like ALM, had issues with the training. 

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 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.

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. 

• Suite management
• Integration with Confluence and JIRA
• Making runs and workflows

A lot of cases can be organised with workflows and become scenario-based.

• Case writing UI
• Better prediction of text

More than one year.

None which I can remember.

No.

The database structure and exploration tool. The API to support integration of the homemade automated testing tool.

This product completes our production line based on continuous integration (using Jenkins) by acquiring all tests results, manual and fully automated into a single platform, which is connected with our bug reporting system (Trac). It offers a full view of test campaigns for each product/version we develop.

The TestRail API to integrate reporting of automated tests is complete, but requires many requests to identify the appropriate entry.

The main room for improvement is in the reporting: It provides templates which are not well adapted and introduces new ones that are rather complex.

Four months.

No issues so far.

With a few users only, but already thousands of items in the DB, we have no issues so far.

Quite good and fast for my interactions with them.

No.

I did not manage it myself, but it seemed straightforward (using the officially supported Linux version).

Pricing for small teams seems correct with respect to competitors.

JIRA/Enterprise Tester: Felt less user-friendly and more complex to start with. Also, it was less adapted for coupling with a homemade automation testing tool.

TestRail is a very user-friendly product to manage test cases. It integrates easily to automation systems and most common bug tracking systems.

It is not the Holy Grail, but has many interesting, useful features.