We changed our name from IT Central Station: Here's why
Get our free report covering Micro Focus, IDERA, Adaptavist, and other competitors of Zephyr Enterprise. Updated: January 2022.
564,322 professionals have used our research since 2012.

Read reviews of Zephyr Enterprise alternatives and competitors

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
Karthik Bhat
Senior Consultant at RXP Services Limited
Consultant
Top 10
Efficient re-usability of action words, but better integration with the JIRA storyboard is needed
Pros and Cons
  • "The data table that helps in converting a single script to multiple test cases is very helpful."
  • "The reporting needs to be improved."

What is our primary use case?

The primary use case is tracking user stories with appropriate test coverage for them, using the BDD framework. Hiptest is mainly used for documenting all of the tests, which we can't do on JIRA.

What is most valuable?

The most valuable feature is the re-usability of action words.

The data table that helps in converting a single script to multiple test cases is very helpful.

What needs improvement?

I was trying to edit something using the raw version that it provides, but it doesn't convert it directly into a test case. Copy-pasting something directly from JIRA requires too much modification and formatting. It would be really helpful if there were seamless conversion when copy-pasting from JIRA directly into CucumberStudio.

The reporting needs to be improved.

Better integration with the JIRA storyboard is needed. By comparison, if you use Zephyr then it automatically appears on the JIRA storyboard, whereas for Hiptest, you need to externally link it. It's not visible to everyone.

For how long have I used the solution?

I have been using Hiptest for about nine months, spanning two projects.

What do I think about the stability of the solution?

This is definitely a scalable solution. At this point in time, we have five to ten concurrent users and we plan to increase our usage in the future.

What do I think about the scalability of the solution?

Hiptest is a stable product.

How are customer service and technical support?

I have not been in contact with technical support.

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

I am part of a consultancy and our choice of tools depends on the client.

Prior to Hiptest, I used Zephyr for a while. One of the main reasons that our client chose to use Hiptest was pricing. Compared to Zephyr, Hiptest is much more economical. There are differences between the two products but it comes at a cost, and Hiptest provides what we want for the lower price.

What other advice do I have?

The suitability of Hiptest depends on the use cases. If you want to document manual test cases and the documentation should be as a programming concept, then you should use it. You can re-use test cases and you can also generate multiple tests from the dataset.

My advice for anybody who is implementing a BDD automation framework is to write the feature files in Hiptest, which will help in designing your automation scripts.

I would rate this solution a six out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Get our free report covering Micro Focus, IDERA, Adaptavist, and other competitors of Zephyr Enterprise. Updated: January 2022.
564,322 professionals have used our research since 2012.