CucumberStudio vs TestRail comparison

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

"CucumberStudio has a very user-friendly interface."

"The solution is stable."

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

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

"Integration with Confluence and JIRA."

"The solution is very stable. We've never had any issues with it."

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

"The integration with Jira and the ability for extra configurations are the most valuable features."

"This is a user friendly solution."

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

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

"The feature that I have found most valuable is the dashboard."

"The reporting needs to be improved."

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

"I would like to see better customer support."

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

"It would be nice to have a description section when creating the test scenario itself so I can indicate what the configuration should be."

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

"The TestRail API to integrate reporting of automated tests is complete, but requires many requests to identify the appropriate entry."

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

"Reporting could be more flexible regarding repeating reports."

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

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

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

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

"The product is not much expensive."

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

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

"Negotiate the best deal you can."

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