@budu Don't forget about the stuff available in the #RubyLang #TTY Toolkit, and testing #CLI apps with Aruba. There's also a book that covers testing such apps with the Aruba gem and #CucumberBDD. IIRC it's entitled "Build Awesome Command-Line Applications in Ruby" by @davetron5000, but it may be out of print. I couldn't find it for Kindle or on the @pragprog website.

- https://ttytoolkit.org/
- https://github.com/cucumber/aruba

@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 *might* 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!