You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
cucumber-features + Aruba is now the official way of testing cucumber.js. This is great. But it would even be nicer to have cucumber.js test itself again, like in its early days. Remember: it emerged by testing itself :)
To achieve this we need:
JS step definitions for cucumber-features (this is easy, those already exist within cucumber_js_mappings.rb)
create the JS mappings between those step definitions and the features ("step definitions of step definitions")
remove redundant features from cucumber-js/features (e.g. progress_formatter.feature); we should keep the number of implementation-dependent features to a minimum, imho.
remove old JS step definitions
Of course, running cucumber-features with cucumber.js won't generate the nice documentation we get from Aruba.
Also, the step definitions won't run the cucumber.js CLI but will directly load a Cucumber.js instance in-memory. At least for now.
The text was updated successfully, but these errors were encountered:
- move JS step definitions from cucumber_js_mappings.rb to .js files
- add a script to run all features at once
- move legacy features to features/legacy
cucumber-features + Aruba is now the official way of testing cucumber.js. This is great. But it would even be nicer to have cucumber.js test itself again, like in its early days. Remember: it emerged by testing itself :)
To achieve this we need:
Of course, running cucumber-features with cucumber.js won't generate the nice documentation we get from Aruba.
Also, the step definitions won't run the cucumber.js CLI but will directly load a Cucumber.js instance in-memory. At least for now.
The text was updated successfully, but these errors were encountered: