A centralized `features/` for each Cucumber implementation? about common HOT 7 CLOSED

Cucumber TCK is such a shared set of features (and step definitions) specifying the behaviour of any implementation of Cucumber. It was started in the early days of Cucumber.js and Cucumber-JVM.

The Cucumber-JVM project lost interest in the TCK but Cucumber.js is still running against the TCK feature suite. We recently merged the TCK features and step definitions into the Cucumber.js repo. The reason is that it was the only implementation still following TCK and we wanted the build toolchain to be simpler.

I still believe a shared feature suite is a great idea to help us keep a high-level perspective on the expected behaviour of Cucumbers.

I'd be more than happy to bring it back to life, if there is any interest. Should that happen, I think we should rework the language used in the feature suite.

from common.

Yeah I thought the TCK was a good idea in principle. My view of why the TCK never got taken up more widely was that the language in the scenarios was too coupled to the UI. Given what we know now, we'd want to make the effort to use domain language in the scenarios, and describe behaviour in terms that would be applicable to the core domain of any Cucumber implementation, as well as its UI.

from common.

Let's bury the TCK and start from scratch

from common.

Let's bury the TCK and start from scratch

👍

from common.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in a week if no further activity occurs.

from common.

This issue has been automatically closed because of inactivity. You can support the Cucumber core team on opencollective.

from common.

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

from common.