David Goss

I'm thinking about the principle of least surprise for this one. As a user, given my intent is something like "putting this scenario title here as a placeholder, coming back...

I don't really see a Scenario as being analogous to a JUnit test. My angle was that it only becomes a runnable test once I actually add some steps and...

On the README side of things for users, I think the cucumber-js one could really use an overhaul. I really like the README for ava In particular: - Logo reassures...

Great - I'll run up a PR for cucumber-js soon and will try and come back with some thoughts on contrubuting docs too.

Broadly agree with @gasparnagy regarding defaults. Specifically my feeling would be: - string - don't default to empty string - array - don't feel strongly either way > Location.column is...

This will be great! I did try to add it a while ago and ran into some issues, but IIRC it was because of some peculiarities in the TypeScript code...

@aslakhellesoy I'm interested in working on this. Would it be okay implemented in JavaScript (using messages, not coupled to cucumber-js) in similar way to html-formatter?

First pass at a JavaScript implementation here: https://github.com/davidjgoss/cucumberjs-junit-formatter Here's an example from a test of what it outputs: https://github.com/davidjgoss/cucumberjs-junit-formatter/blob/main/test/snapshots/integration.test.ts.md It's wrapped as a cucumber-js `Formatter` class, but doesn't use any...

@aurelien-reeves pickles from the same feature file could have the same name if: - You have a scenario outline with examples (unless the name includes a parameter) - People have...

@luke-hill true - I forget that the rule name doesn't contribute to the pickle name