Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unify features with cucumber-features #21

Closed
jbpros opened this issue Jul 26, 2011 · 1 comment
Closed

Unify features with cucumber-features #21

jbpros opened this issue Jul 26, 2011 · 1 comment
Assignees
Labels
📖 documentation Improvements or additions to documentation
Milestone

Comments

@jbpros
Copy link
Member

jbpros commented Jul 26, 2011

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.

@ghost ghost assigned jbpros Jul 26, 2011
jbpros added a commit that referenced this issue Jul 26, 2011
- 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
@jbpros jbpros closed this as completed in bcab1b5 Jul 28, 2011
@lock
Copy link

lock bot commented Oct 25, 2018

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.

@lock lock bot locked as resolved and limited conversation to collaborators Oct 25, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
📖 documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

1 participant