Add support for Gherkin / Gherkin Spec

Although we have have BehaviorSpec, a big necessity that I’ve been observing in some projects that test Java/Kotlin code is using the CucumberRunner.

With tests written in Gherkin, a team can generate a powerful suite of tests that are read from a .feature file, in natural language, and then transform it into code.

However, the code written to be executed by CucumberRunner is quite Cucumbersome (~see what I did there riaria~), and it leads to easy to understand specification feature file, but often hard to understand executable code, and hard to setup too.

I propose we implement a Gherkin Spec, that would read from a configurable file and execute the scenario based on that .feature file.

If we believe this is a good feature, I’m glad to enhance this small feature request to a more robust suggestion.

[sksamuel]

Personally I think cucumber is total shit. The reason is when I was forced to use it about 5 years ago I had to create loads of text files, loads of annotations, and put together tests in a way that was 10x slower than just writing them in code properly.

The rationale - that “non techies” can read the tests. Well that’s nonsense - BA’s can’t write cucumber tests anymore than they can write scalatest.

If you want to come up with another spec, that’s elegant and read from a file, crack on, but I don’t want to see anything as bloated and crap as cucumber.

[LeoColman]

I think that with the additions from #562 BehaviorSpec got better, and there’s no longer a real need for something stronger that the BDD implemented there.

Because of this, I’ll be closing this issue