CucumberStudio vs TestRail comparison

"The URL is very useful, and it has a very good UI for deploying information of the scenarios created."

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

"The most valuable feature of CucumberStudio is its use of action words, which allows me to avoid writing test cases from scratch for the most common scenarios."

"CucumberStudio aligns with our strategy for data-driven testing."

"CucumberStudio aligns with our strategy for data-driven testing."

"The solution is stable."

"CucumberStudio has a very user-friendly interface."

"The best thing is that a person without knowledge about the program can easily understand what happened in our testing process."

"You don't need to follow complex procedures to create a test run, test case, etc."

"Reliable and stable. It is important that TestRail be up and running 24/7 as we have users around the world using it."

"I use the solution for test management."

"It's very easy to use and simple with a low level of complexity. There are pros and cons with complex tools, but the advantage of TestRail is that it fits in really well with an agile life cycle."

"I use the product to create test cases and share them with my team and manager."

"The API to support integration of the homemade automated testing tool."

"I haven't faced any stability issues using the solution. Stability-wise, I rate the solution a ten out of ten."

"The product helps us create test cases and reports."

"Another kind of deployment might be useful, perhaps an option to install the tool in a local deployment."

"I think it would be better if we could also do the reporting with CucumberStudio."

"CucumberStudio's API integration could be improved both in terms of reliability and design."

"The reporting needs to be improved."

"A key area for improvement is to revamp outdated components such as HipTest publisher."

"I would like to see better customer support."

"A key area for improvement is to revamp outdated components such as HipTest publisher."

"I have faced some issues with the integration between TestRail and Jira, which haven't been permanently resolved yet."

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

"Better prediction of text."

"The test suite management has room for improvement as well as better reporting."

"Customer support could be enhanced. All the support is provided via chat and emails. Sometimes, you really need to speak to a person, and arranging such calls is not easy."

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

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

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

"Pricing for small teams seems correct with respect to competitors."

"I give the price a five out of ten."

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

"The product has a reasonable price in terms of the features."

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

"The solution is quite reasonably priced for what it offers and offers a monthly subscription model."

"My advice to others is to shop around for the best deal. Some options out there are free in cyberspace."

"Use TestRail Cloud (online TR hosted server) and don't worry about maintenance or scalability. It saves a lot of cash and time."