TestRail Reviews

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. 

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.

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. 

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.

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.