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.

View full review »

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.

View full review »

TestRail lacks the functionality to map test cases to requirements and risks. While integration with another tool is a workaround, it doesn't fully meet my needs. Additionally, I would appreciate AI features that help design test cases based on documented requirements and validate the quality of requirements for testability. View full review »

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.

View full review »

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.

View full review »

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.

View full review »

TestRail should improve its pricing. 

View full review »

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

View full review »

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. 

View full review »

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.

View full review »

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.

View full review »

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.

View full review »

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.

View full review »

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.

View full review »

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.

View full review »

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. 

View full review »

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. 

View full review »

• Case writing UI
• Better prediction of text

View full review »

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.

View full review »

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.

View full review »

It would be nice if they would add an export to Word.

View full review »

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.

View full review »

Only a few small ones. Reporting could be more flexible regarding repeating reports. You have to basically repeat the same report run, but then you have two reports. An old one and a new one. A 'refresh' option for reports would be very useful. This way you would have a report but just need to refresh its data when needed. Also, more flexibility in adding custom fields and their placing around the test case form would be beneficial. For example, sometimes I can't place a custom text (paragraph) field in the exact spot that I was planning. Again, nothing critical, just a few small improvements.

View full review »

The platform needs improvement regarding performance and creating links.

View full review »