CucumberStudio vs TestRail comparison

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

"The solution is stable."

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

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

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

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

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

"The product’s most valuable feature is the UI. The structure of test cases is easy to understand."

"The most valuable features are the flexibility, ease of use for writing new test cases, the test plans, and the composition."

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

"Integration with Confluence and JIRA."

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

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

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

"I would like to see better customer support."

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

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

"The reporting needs to be improved."

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

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

"The platform needs improvement regarding performance and creating links."

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

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

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

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

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

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

"The reports should be more user-friendly."

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

"Negotiate the best deal you can."

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

"The product is not much expensive."

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

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

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