David Goss

Thanks @vitalets. With that specific example of tag-filtered step definitions, those aren't a first-class Cucumber concept, so I'd be a little hesitant to add them to the core library. An...

> The expected behavior should be for every undefined step in a feature file with 'Scenario Outline' should show a warning for unimplemented steps. Can you elaborate on the behaviour...

Thanks for raising @vlevkoniuk. You're right that both formatters don't write anything to the file stream until the test run finishes. There is, I think, a sort of unwritten principal...

The the Cucumber Reports service is unfortunately in a state of limbo at the moment pending SmartBear's divestment from Cucumber, see https://mattwynne.net/new-beginning I'll keep this open as it seems a...

@grasshopper7 that looks good. Think it would also need BEFORE_ALL and AFTER_ALL

This is currently needed because a source file is generated with the package version number. The usage is in cucumber-js when we generate the `meta` message: https://github.com/cucumber/cucumber-js/blob/6eede88fe6e6aed83a1ac581740d179e09643e3b/src/cli/helpers.ts#L105 I don't think...

A bit of a chicken and egg problem with the perl tests here - they rely on the current published version of the CCK, whose messages don't include the new...

I originally added `testRunStartedId` to the `TestCase` message here. I've since removed that, having reconsidered. I think there's an argument that, given the (currently theoretical) scenario of multiple test runs...

> In that situation you'd want to be able to associate the compiled test case with the test run. Getting that information up-front would mean you knew how many results...

I'm definitely supportive of having titles on links for the reasons you say, and that interface looks good to me. The question is more how we map it to the...