multiple-drag-n-drop VS cucumber-ruby

There are many ways, articles, and best practices on how to install and configure unit tests, and explaining it, will require a separate (or maybe more than one) article. And my goal here is to acquire basic knowledge of unit testing with Cucumber and cover the main functionality of the application that you developed in the last part. Therefore, all dependencies and configurations will be as simple as possible and minimally necessary for writing tests. Here is the list of required dependencies and dev-dependencies, which you also can find in the package.json file:

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.