cucumber-ruby VS Cucumber.js

It's a custom built "framework" that uses all the tools the big guys use but without any of the cost they demand. Which means we can make it bark like a dog if we want to. We use Cucumber for our test scripts, that gives us a clean and easily readable format that everyone from the CEO to Mike from Canmore can write, we use TestNG to package those test scripts and run them in parallel using a class that extends AbstractTestNGCucumberTests, we trigger the executions with xml files. Everything is packaged by maven and that allows us to execute on the command line (in a relatively clean way) and that allows us to easily execute the framework using something like Jenkins pipelines. We've also set up profiles in our POM.xml file so we can pass parameters on the command line and execute a specific test: something like mvn clean test dTest=TEST-1408 dPlatform=android dVersion=13 dbrowser=chrome. Or we can say something like mvn clean test dFull and that will test every regression test we have against every platform we support. These command line parameters are used to fill in the folder names of paths to the specific file.

Behavior driven development looks like a good idea and popular frameworks like cucumber have a ton of features and available material ... for other languages that is, since the official site mentions the C++ framework as unmaintained

For both of them, I use cucumber and a test look likes

there are many frameworks, we use cmocka for unit tests. For integration tests my understanding is that everyone pretty much rolls their own solution (we use cucumber to drive them).

Cucumber.

did you mean cucumber.io ? will check it out, thanks mate

What you're describing is most commonly known as acceptance testing, or behavior-driven tests. There's an excellent framework for this called Cucumber. They have gems for both plain Ruby and Rails.

What you're describing is most commonly known as acceptance testing, or behavior-driven tests. There's an excellent framework for this called Cucumber. They have gems for both plain Ruby and Rails.

It is a known fact that before any developer pushes the code (either to the development environment or Staging environment before migrating to the Production environment), he would be performing unit testing on the code changes that he has made. For unit testing, developers have a variety of unit-testing frameworks to choose from. JUnit and Jasmine are the most popular unit-testing frameworks. Other types of tests performed at a module/package level are functional tests and visual regression tests. Cucumber is a popular choice for Behavior-Driven Development (BDD) or functional testing, and a visual screenshot comparison tool named Wraith is preferred for performing visual regression testing.

Some BDD frameworks such as JBehave, RSpec, Mocha, Jasmine, Cucumber, among others, embrace the use of this template. Spek is not an exception to this rule. The main difference is that it doesn’t force you to use a concrete assertion framework or additional behavioral files (e.g Cucumber or JBehave).

There are a lot of more or less good testing frameworks in the wild. Some of existing testing frameworks doing their job very well and are de facto a standard, like a "cucumber" for BDD testing.

Just to add, anyone who is curious to learn more about BDD I would recommend checking out the Javascript flavor of Cucumber. It's cool stuff and immensely useful! https://github.com/cucumber/cucumber-js

And pretty deep into that rabbit hole you get Cucumber and the Gherkin language (https://cucumber.io/); project managers write "natural English" unit tests, but to get them to work, the developers write essentially a chatbot interpreter to process the files and run them.

Cucumber is an automation tool based on the BDD framework, using which you can write automated acceptance tests for web applications in the Gherkin language.

Many testing frameworks use Domain Specific Languages (DSLs) to define tests in plain English. Perhaps the most notable example is Gherkin, the language used by the Cucumber testing framework: