@alexanderadam @miry You're making a fair point. I'd argue that such is a failure in the agile implementation rather than in #CucumberBDD or #Gherkin itself, though.

That doesn't invalidate your point. It just turns it from "Cucumber is a useless tool!" into "We're failing to collaborate effectively with stakeholders." The latter is a process problem, and should be addressed within the #ProjectManagement framework being used IMHO.

Good call-out, though!

@smortex Interesting idea. #RubyLang #CucumberBDD could call out to compiled #CrystalLang code, so I suppose it would simply force the team to think more about the behavior of a running system, not intermixing specs and steps as is often the case in Cucumber.

The biggest challenge would likely be in testing the results, since (unlike with Ruby). I *migh*t not be able to use some of the DB rollback plugins and such.

It's actually a great idea. Thank you for the constructive suggestion!

#CrystalLang comes with its own version of #RSpec built in. However, I can't seem to find a Crystal equivalent for #CucumberBDD, although I've heard anecdotally that Turnip (which embeds #GherkinSyntax into RSpec) works even if it lacks some of Cucumber's full feature set. What do Crystal programmers use as a drop-in replacement or alternative implementation for #RubyLang Cucumber?