CucumberStudio Reviews

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.

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.

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.

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.

• The auto-completion while writing test steps. It is very useful to avoid test step duplication.
• The test steps refactoring. This is useful to reduce test maintenance.
• The strong automation abilities.
• the Atlassian JIRA plugin is very efficient to link development tasks to test scenarios and follow your test coverage and results.

Hiptest allowed us to clean up our test campaigns and standardize the way we write test cases and structure our BDD approach.

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.

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.

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.