We changed our name from IT Central Station: Here's why

TestRail by Gurock OverviewUNIXBusinessApplication

TestRail by Gurock is #11 ranked solution in top Quality Management Tools. PeerSpot users give TestRail by Gurock an average rating of 6 out of 10. TestRail by Gurock is most commonly compared to Zephyr Enterprise: TestRail by Gurock vs Zephyr Enterprise. The top industry researching this solution are professionals from a computer software company, accounting for 30% of all views.
What is TestRail by Gurock?

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. Efficient test management, get started today!

Buyer's Guide

Download the Test Management Tools Buyer's Guide including reviews and more. Updated: January 2022

TestRail by Gurock Customers

Apple, Microsoft, Boeing, Intel, NASA, Amazon, HP, Samsung

TestRail by Gurock Video

TestRail by Gurock Pricing Advice

What users are saying about TestRail by Gurock pricing:
"Its price is definitely not more. If they introduce automation, they can charge more."

TestRail by Gurock Reviews

Filter by:
Filter Reviews
Industry
Loading...
Filter Unavailable
Company Size
Loading...
Filter Unavailable
Job Level
Loading...
Filter Unavailable
Rating
Loading...
Filter Unavailable
Considered
Loading...
Filter Unavailable
Order by:
Loading...
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Search:
Showingreviews based on the current filters. Reset all filters
Lead Engineer - Automation
Real User
Top 20
Increases overall testing productivity, but not an automation-driven solution
Pros and Cons
  • "The feature that I have found most valuable is the dashboard."
  • "With TestRail, the APIs are there, but they may not be able to easily integrate with the Jenkins."

What is our primary use case?

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.

How has it helped my organization?

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.

What is most valuable?

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.

What needs improvement?

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.

For how long have I used the solution?

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

What do I think about the stability of the solution?

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

What do I think about the scalability of the solution?

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.

How was the initial setup?

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.

What's my experience with pricing, setup cost, and licensing?

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

What other advice do I have?

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. 

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
Quality Assurance Manager at a financial services firm with 10,001+ employees
Real User
Top 20
Good management from the testing perspective, but needs a lot of improvements from the quality assurance perspective
Pros and Cons
  • "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."

What is our primary use case?

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.

What is most valuable?

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.

What needs improvement?

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.

For how long have I used the solution?

I have been using TestRail for two years.

How are customer service and technical support?

I have not contacted technical support.

Which solution did I use previously and why did I switch?

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.

What's my experience with pricing, setup cost, and licensing?

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

What other advice do I have?

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.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.