mlncn
Elixir has potentially great support for Behavior Driven Development and writing tests in the well-known Gherkin language, but online searches lead to a plethora of abandoned projects— and three-to-four maintained ones, whose relationship to one another is unclear:
- cucumber_gherkin, with regular releases, maintained officially by Cucumber itself (though not listed) but nothing depending on it.
- cucumber, with a release as recently as June, and much more approachable documentation, depends on neither of the above nor nothing at all, and nothing depends on it.
- cabbage, which requires gherkin, both last updated in 2023. Appears to be the most-used but the documentation is so-so.
- ex_cucumber, last updated in 2022, which requires ex_gherkin, last updated 2021, has extensive but less approachable documentation (even the basic usage in the README. This one at least acknowledges the existence of one other option, cabbage, calling out several things including the lack of “multi-language support” and no support for Background (which is still listed as still pending on cabbage’s roadmap).
So there are four totally independent efforts despite an official Cucumber-maintained package with the most regular releases? And no one has written about their process of choosing one of these? That is the state of things for people wanting to get started with writing BDD-style tests in Gherkin syntax for their Elixir project?
Maybe we can improve on that a little in this topic…
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Supporting innovation across the BEAM ecosystem.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #blog-post
- #ai
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Producing high quality Elixir screencasts since 2017.
**Building the future of software with AI, trust, and human connection.**
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 3- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
dimitarvp
Well, welcome to open source. People check another project, say to themselves “I would do it another way” and there you go, you arrive at today’s state of affairs.
More seriously, I would just try to use 2-3 of those with multiple very concrete tests that must be 100% clear beforehand (i.e. you know exactly what you want to test) and evaluate for yourself.
trisolaran
I haven’t worked with Elixir professionally since March 2024 now, but in my last project I was using BDD tests with
cabbage. I picked it overtex_cucumberprobably because it was the most used package (don’t recall exactly).cucumberdidn’t exist back then, but it seems worth trying.sanswork
I think part of the problem is most people abandon BDD pretty quickly. So someone gets really excited about it, like @dimitarvp mentioned doesn’t like the existing implementations then starts their own then realised BDD isn’t that great and move on abandoning development in the process.
BDD is dying/dead as a process these days for the most part so its not going to get a lot of attention. If you really like it a blog post outlining your findings would be a good place to essentially solve your problem for future people.