Looking for maintainers

[meadsteve]

I've not had the time I'd like to commit to this project recently (TLDR; I've got a demanding newborn baby!).

I'm looking for anyone (ideally a few) who'd be interested in maintaining this project.

Please comment on this issue if you are interested.

[kennyp]

@meadsteve even though I'm just getting started with white-bread I would be happy to lend a hand. Do you have an outline for features you would like to see next that folks could start working on?

[leifg]

I can take some tasks from time to time but I'm not the best person for this as I am far from working full time with cucumber.

Does it make sense to merge this project with cabbage-ex/cabbage or at least use cabbage as a base for the execution?

[meadsteve]

At the moment I don't really have any roadmap for this. I'd be happy for this to be fully merged with cabbage. The main difference as I see it is cabbage is built on top of exunit whereas I build whitebread as a standalone tool. So the only reason for both projects to exist is if there are some benefits to keeping separate from exunit.

[daveed-al]

@meadsteve I would be interested in contributing to this project. Please let me know what needs to be done to be a cucumber implementation.
I would like to use the concept of "World" in Cucumber https://github.com/cucumber/cucumber/wiki/Configuring-the-Scenario-Execution-Context-(World)
Is it something that has been done and if not would it make sense to do it as there is no instance in Elixir?

[marnen]

@meadsteve:

So the only reason for both projects to exist is if there are some benefits to keeping separate from exunit.

That's a big benefit. I use ESpec, not ExUnit, and Cabbage's dependence on ExUnit turned me off.

[meadsteve]

@marnen might be interesting to see how easy it'd be to convert Cabbage to run on Espec. That way you could have an adapter that plugs in ESpec and an adapter that plugs in ExUnit.

BYOTR - Bring your own test runner.

[marnen]

That's an interesting idea, though I'm probably not experienced enough in Elixir to do that anytime soon. I also am not sure I like that approach architecturally...

[marnen]

...compare cucumber-ruby, which is completely agnostic about which test framework it uses; the steps just call arbitrary Ruby code. I think that's the proper model for such a tool.

[marnen]

All of this is to say that while Cabbage is clever, I think it's fundamentally barking up the wrong tree, and instead of putting the effort into writing an ESpec adapter for Cabbage, I'd rather put it into helping white_bread (or something like it) succeed.

[ringods]

@marnen the big reason for me to split the test framework (in this case BDD) from the test runner is that you can use all other additions/plugins which build on top of a certain test runner.

As an example, in my day job I have been working on a pytest plugin for the mamba BDD framework. However, the mamba team implemented framework and runner in a single tool, hereby dropping all support for other pytest plugins. In our case, the team needed this one: pytest-reportportal.

[marnen]

@ringods Interesting, but I'm not sure how you mean that to apply to White-Bread/Cucumber/Cabbage/etc. Can you clarify?

For myself, the main decoupling that I care about is that the Gherkin step runner should not be coupled to any test library (or anything else) in the step implementation. I like the idea of decoupling the rest runner further, but for me at least it's of secondary interest.

[marnen]

@ringods Also see #96.

[Kosmas]

@meadsteve I would like to help in any way possible. Have been the maintainer for cucumber-rails for quite some time, but have not been using rails a lot lately. And my next project will be in Elixir so I would be using white-bread hopefully. If there's anything I could help with, please let me know.

[victorolinasc]

@meadsteve I see plenty of people are volunteering to maintain the project. Do you or anybody else have any updates on this?

I am starting some BDD discussions where I work and I think that a well updated library is due on the community. I can help too if there is need.

Was just wondering the state of things here. Cabbage seems un-maintained currently. It does not compile on Elixir 1.7 and there has been no activity from the lead maintainer on Github as a whole was January this year. So, I am thinking that betting here is a safer bet for the future.

Thanks for your work and wish you good luck on your next adventures.

[meadsteve]

So it turns out I missed some notifications for this issue 😳. I've actually a little more time than when I opened this issue. So I've been applying bug fixes and reviewing small features.

What I won't have time for is stearing the future direction of this project. So ideally I'm still looking for a few people to take on a role like this.

[karlosmid]

Would like to be part of this project.

[meadsteve]

I got a bit swamped and ignored this thread for a while. I'm starting a new more relevant one