CucumberStudio enhances software testing with BDD-style Gherkin syntax, supporting code integration and data-driven testing, streamlining test management for agile teams.
| Product | Mindshare (%) |
|---|---|
| CucumberStudio | 0.8% |
| Microsoft Power Apps | 7.8% |
| Oracle Application Express (APEX) | 4.9% |
| Other | 86.5% |
| Company Size | Count |
|---|---|
| Small Business | 3 |
| Midsize Enterprise | 3 |
| Large Enterprise | 3 |
| Company Size | Count |
|---|---|
| Small Business | 27 |
| Midsize Enterprise | 17 |
| Large Enterprise | 30 |
CucumberStudio facilitates effective test management through robust features, promoting re-usability of action words and seamless third-party collaborations. It integrates smoothly with JIRA and other frameworks, simplifying processes with its intuitive interface. Scenarios and test runs boost testing speed and execution efficiency. However, improvements in JIRA conversion, API integration, and reporting are needed, alongside enhanced support for global users and expanded deployment options. Users find the framework beneficial for tracking user stories with comprehensive test coverage while automating scenarios for mobile and software applications. Planning and documenting tests become seamless as it aligns with project management tools.
What are the standout features?CucumberStudio is widely applied for tracking user stories and ensuring aligned test coverage in industries utilizing BDD frameworks. It facilitates seamless automation of test scenarios within mobile and software development, fostering efficient integration with infrastructure routines, thus supporting comprehensive project management and execution.
CucumberStudio was previously known as Hiptest.
Cisco, Cardinal Health, Intuit, Smartbox, Accenture, Deliveroo
| Author info | Rating | Review Summary |
|---|---|---|
| Technical Expert at Bertelsmann SE & Co. | 3.5 | We use CucumberStudio to design and automate test scenarios and integrate with our infrastructure. Its data-driven testing aligns with our strategy, though outdated components need updating. It requires customization but delivers a good ROI and collaborates well with Jira. |
| Manager in Quality and Processes at a transportation company with 1,001-5,000 employees | 4.0 | I use CucumberStudio for storing and planning test cases, integrating with Jira for seamless management. Its action words and Gherkin syntax enhance test processes, although API integration and reporting need refinement. Testing efficiency has improved despite challenges in measuring ROI. |
| Support Engineer at a computer software company with 11-50 employees | 4.0 | I use CucumberStudio to create scenarios for mobile applications with behavior-driven development. Its URL feature and UI are valuable for deploying scenario information. However, I wish it offered local deployment options. I haven't used other similar products. |
| Software Test Engineer at MK Consultancy (UK) LTD. | 3.5 | I use CucumberStudio for writing test scenarios and code implementation. Its user-friendly interface and helpful documentation accelerated our compatibility testing. Although customer support needs improvement, I find its integration with Amazon Web Services beneficial. |
| Software Test Engineer at Qestit | 3.5 | CucumberStudio allows easy comprehension of testing processes by those without programming knowledge. Its best feature is scenario editing. However, it lacks reporting capabilities, has stability issues, and needs automatic scenario-to-code connection. It’s deployed on Microsoft Azure. |
| Senior Consultant at RXP Services Limited | 3.0 | I use Hiptest for BDD test documentation, appreciating its reusable action words and data tables. However, I find JIRA integration and reporting need significant improvement. While it's an economical Zephyr alternative, I rate the solution 6/10. |
| Senior Software Test Engineer | 4.0 | I find HipTest excellent for its end-to-end BDD testing, saving time, simplifying test management, and strong third-party integrations. Technical support is great, though improvements are needed in exporting repeatable action words. |
| QA Engineer at a tech vendor | 4.0 | I found the solution's automation features, keywords, and tags saved time and improved mobile test coverage, with simple setup and no issues. I wish there were more tutorials and examples, and a larger basic license. |
| Sr QA Analyst / Water Street at a tech services company with 51-200 employees | 4.0 | I find Hiptest valuable for creating and running test cases, especially with cloning features that save time. However, it has stability and scalability issues with large data tables, sometimes losing my data due to memory problems. |
| Head of Software Development Lab at a logistics company with 501-1,000 employees | 4.0 | For 18 months, I've valued its test script refactoring and efficient campaign management. Setup was easy, and support is good. My main suggestion is improved reporting and metrics, especially historical and cross-project. |
CucumberStudio is primarily used for designing test scenarios and automating testing. We have implemented it in conjunction with our own routines for integration into our infrastructure.
CucumberStudio aligns with our strategy for data-driven testing. It supports our product owners in designing test scenarios effectively. The tool allows for the seamless integration of test scenarios with our existing system using the API provided by CucumberStudio. The collaboration with Jira enhances the overall efficiency.
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.
We've been working with CucumberStudio since last March.
Their technical support scores around five to seven out of ten in my opinion. It is sufficient in understanding CucumberStudio but does not meet all of our specific needs. More tailored help would be beneficial.
Neutral
The setup was more of a legacy implementation using existing frameworks such as Behave and Playwright in conjunction with CucumberStudio.
We conducted the implementation with the help of advisors.
It paid off and worked out well, but it required alignment with our specific project needs and processes.
We use a concurrent model of approximately one thousand euros per user, which is quite appropriate for our needs. The pricing model is convincing compared to other products evaluated.
From my perspective, the outdated components in CucumberStudio should be updated to give more support to users, especially for initial synchronization. I would rate CucumberStudio around seven out of ten.
I use CucumberStudio as a test case repository. All of our test cases are stored there. It is also part of our test planning process. For every sprint, we plan the test cases in CucumberStudio and integrate it with project management tools such as Jira. This enables us to link user stories in Jira with CucumberStudio and track our test cases.
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. Moreover, CucumberStudio's support for code integrations and API calls is excellent. The platform provides the benefit of unlimited read-only accounts, enabling various roles like engineers and product managers to review test cases and results. The structure of CucumberStudio is also commendable, as it supports BDD style Gherkin syntax, which is useful for our test management processes.
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.
I have been working with CucumberStudio for about five years.
CucumberStudio is stable for the most part, although there have been a few outages, both planned and unplanned. However, these outages were infrequent. Overall, it worked well most of the time.
CucumberStudio is a scalable cloud-based solution. The scalability depends on the number of user accounts, allowing us to scale according to our needs.
I contacted SmartBear support a couple of times for feature requests and during downtimes. They were quite responsive.
Neutral
I have used other test management tools in the past, but I'm not using any currently.
The initial setup was easy. Since it is a cloud-based solution, we only needed to create our accounts.
Testing efficiency improved, but it is difficult to quantify the benefits in terms of money.
CucumberStudio was affordable for us. We negotiated good deals with SmartBear, and affordability can vary based on individual perspectives.
For teams following a BDD style software development approach, CucumberStudio is a great collaborative tool that covers all the basic requirements of a test management tool. I would rate CucumberStudio an eight out of ten.
CucumberStudio is used to create a scenario of a mobile application that uses behavior-driven development. It is used to create scenarios in software development.
The URL is very useful, and it has a very good UI for deploying information of the scenarios created.
Another kind of deployment might be useful, perhaps an option to install the tool in a local deployment.
The solution is stable. I rate it a ten out of ten for stability.
Regarding scalability, there is a need for more users and licensing to accommodate that.
I have not used the customer service support, so I do not have information about that.
Positive
I have not used another DAST kind of product before.
The setup is very simple since it's SaaS and does not require deployment.
I would recommend CucumberStudio to others because it's a very useful tool and easy to start using.
I'd rate the solution eight out of ten.
CucumberStudio is used to write test scenarios and implement codes.
CucumberStudio has a very user-friendly interface. The customer support was prompt, and the documentation was good. Using CucumberStudio in our workflow has sped up compatibility testing.
I would like to see better customer support.
I have been using CucumberStudio for five to six months.
We haven’t faced any stability issues with CucumberStudio.
Seven people from my team work with the solution.
The solution’s initial setup is easy.
CucumberStudio's implementation is easier than that of other products like GitHub. It is easy for somebody to learn to use CucumberStudio for the first time because the annotations interface is very basic.
Overall, I rate the solution a seven out of ten.
With CucumberStudio, we can see the exact style of the project. For example, we don't see just the programming page in our project, but there is one page for scenarios. The scenario is readable for people that don't know programming. They can see and they can understand this best scenario.
The best thing is that a person without knowledge about the program can easily understand what happened in our testing process. They can see the report and change some keys in our scenario in the CucumberStudio, which is the best feature.
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 have been using the solution for more than one year.
There are stability issues with the solution. Sometimes because of the update, there are problems. I do not know the error, but when setting Cucumber for the scenario, it will change, and I have to search the Internet for the new update. But I think it should be updated automatically.
It is a scalable solution. In my last company, there were around 40 users using CucumberStudio.
The initial setup is easy.
I recommend the solution as it's easy to use.
I rate the solution seven out of ten.
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.
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.
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.
I have been using Hiptest for about nine months, spanning two projects.
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.
Hiptest is a stable product.
I have not been in contact with technical support.
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.
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.
The supporting the writing of test cases following Behavior Driven Development, and then exporting the test cases into automation code. After writing the automation code, again pushing the results back into HipTest automatically. So it supports an end-to-end testing cycle very efficiently, saving time.
Its integration with third-party tools like JIRA, Confluence, Git, Jenkins, etc is also great. Makes this tool awesome.
Previously it was difficult to manage test cases and their results, but using this tool makes it easier to manage the testing life cycle. You can easily manage the regression of automated test cases and get the status of test cases automatically.
It needs some improvement when exporting scenarios into automation code, to make it easier to manage the repeatable action words and tests.
One year.
No.
No.
10 out of 10. They are very good in technical support.
Yes, I used HPE QC, but it is a vast product and not easy to manage. It also does not provide good support for automation of test cases.
Using HipTest makes the testing process easy and its support for Behavior Driven Development helps align all the team members, whether technical or non-technical.
Its feature of exporting scenarios into automated test cases in any testing framework is awesome.
It is straightforward. I set it up on my premises with a little bit of support from HipTest.
It depends on your organization size, but its pricing is not too high. For 25 users it's $8/month for each user. For three users it's free.
Yes, I evaluated tools like Zephyr, TestRail, etc.
Before implementing this you must know about Behavior Driven Development and Agile. Then you will be able to get the most out of it.
Integration with automation frameworks, keywords, and tags. It allows for saving time writing test cases and implementing automation.
We've covered some complicated mobile features with Appium auto tests faster.
More tutorials and examples.
Less than a year, almost 8 months.
No.
No.
I haven't tried it.
On the current project, it was an initial solution.
It was simple. The product itself is perfect for fast and non-bureaucrat development (let’s say agile).
Make the basic license larger (it has 3 accounts; it's better to have 5).
I joined the current team when they were already using Hiptest. Previously, I worked with MTM from Microsoft, but it’s hard to compare as they have a different feature coverage and purposes.
Try examples first, it will be clear whether you need this product or not.
Scenarios, since is a really easy way to create and control your test cases.
Test runs, since it lets you execute the test cases in a faster way. You can included screenshots or notes, or to mark it as passed, failed, retest, and some others.
Cloning Scenarios, which save you a lot of time when you have to create test cases for a regression or for similar tasks.
I was not part of the company before they started using Hiptest, but they told me they created their test cases in Excel. Now they can create test cases faster, even cloning their own information.
It has some issues that they can fix. If you start creating a data table, and you insert values really fast, then it doesn't save some of them.
I think they should improve the way the memory is handled in areas where the app is really heavy because of JavaScript.
Since January.
Yes, it is not stable when you create a data table that includes more than 30 elements, so it can lose your data.
As mentioned before, it has issues depending on the input size of the data.
The support is fast.
I don’t know it the company used to have a previous solution.
It took a while to understand most of the things. Not too complex, but also not too straightforward. Hiptest has a lot of functionalities to understand.
Not applicable.
Not applicable.
It’s a really good product. It has some flaws, but it is going to make your life easier.
The ability to manage and refactor test scripts using action words, and the ability to create skeleton codes for test automation.
It has allowed us to efficiently manage our test cases, tracking all our test campaigns both manual and automated.
The reporting and metrics can be improved. E.g.: If we wanted to have metrics across all projects.
Test run for an automated test could have historical data to better track our progress and effectiveness.
18 months.
No.
No.
An eight out of 10. They respond quite fast (in few hours) and are very open-minded.
I use manual test case management using a spreadsheet and have reviewed several test case managements.
Most of them are very cumbersome to manage and track, especially on the test script refactoring and test campaign.
It's easy. It's on the cloud. We could import our test scripts and start right away.
First three users are free. It should be enough to get the feel of it before committing to it. Plus per user price is USD$ 8-11 and you can have volume discounts.
TestLink, TestLodge, and few others that i have forgotten the name.
The power of Hiptest is its test cases and campaign management. If you're into test automation, they can help you boot. But to really get a sense of how it is integrated with test automation, you really need to try it with your case.
