Eric Kessler

> * yard-cucumber is a nice idea but the project hasn't seen any updates since 2018 and only works with cucumber 2 and 3. I have looked into updating the...

> I think that what I'm hearing is you'd like each pickle to have an identifier (ID) that is: > > 1. unique within the whole set of possible pickles...

> I guess it depends on what we consider to be "reasonable modifications" Any modification is a 'reasonable' modification. ;) Don't like the name of a test? Change it. An...

> Manually tagging is such a horrid solution though. I get your points, but it soooo, soooo would > interfere with the fluency of the whole process. *Manually* tag things?...

> I would love to try and find a solution that didn't involve putting additional stuff into the Gherkin text if possible, manually or automatically. Unfortunately, it is the only...

I'm late to the party on this one but, for what it's worth, I see outlines test generators and backgrounds as test adjusters. So not pickling an outline without example...

@aslakhellesoy According to our [test](https://github.com/cucumber/cucumber/blob/master/gherkin/testdata/good/incomplete_scenario.feature) data, [no](https://github.com/cucumber/cucumber/blob/master/gherkin/testdata/good/incomplete_scenario.feature.pickles.ndjson). Previous behavior: no pickles created for a scenario without steps. Current behavior: pickle created for a scenario without steps but _steps from a...

Cucumber executing a test that got written down is a feature, not a bug. If you don't want a test to to run because it isn't finished yet, that is...

@aslakhellesoy Fun fact: I ran into this use case just the other day. I had a couple complete scenarios that had common enough setups that a `Background` had been made....

> I think that empty scenarios should be treated like an ordinary scenario. Execute all the before/after hooks, but not any steps (because there are none). It makes it much...