Manager in Quality and Processes at a transportation company with 1,001-5,000 employees
Real User
Top 20
2025-04-16T08:57:00Z
Apr 16, 2025
CucumberStudio's API integration could be improved both in terms of reliability and design. The API requires data to be sent in a specific format, which takes time to build. Additionally, the reporting features could be made more intuitive.
A key area for improvement is to revamp outdated components such as HipTest publisher. Introducing modern technology could improve the platform. API-based solutions are present but could benefit from being more up to date.
Presently, when I work with Selenium, I need CucumberStudio just to make my project readable to other people, and for reporting, I use Maven. I think it would be better if we could also do the reporting with CucumberStudio. There are issues with stability, and the automatic update feature is missing. Since not all people do not have knowledge about programming so if there is some automatic method of connecting the scenario to step definition to code then it would be easy and help people gain good knowledge in programming.
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.
Rapid Application Development Software accelerates the process of creating software applications by focusing on quick iterations, user feedback, and an adaptive development process. It is ideal for projects requiring fast delivery while maintaining flexibility and scalability.This category of software facilitates the development of applications through an iterative approach, allowing for quick adjustments based on user feedback. The flexibility in design and specification adjustments means...
CucumberStudio's API integration could be improved both in terms of reliability and design. The API requires data to be sent in a specific format, which takes time to build. Additionally, the reporting features could be made more intuitive.
A key area for improvement is to revamp outdated components such as HipTest publisher. Introducing modern technology could improve the platform. API-based solutions are present but could benefit from being more up to date.
Another kind of deployment might be useful, perhaps an option to install the tool in a local deployment.
I would like to see better customer support.
Presently, when I work with Selenium, I need CucumberStudio just to make my project readable to other people, and for reporting, I use Maven. I think it would be better if we could also do the reporting with CucumberStudio. There are issues with stability, and the automatic update feature is missing. Since not all people do not have knowledge about programming so if there is some automatic method of connecting the scenario to step definition to code then it would be easy and help people gain good knowledge in programming.
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.