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

Target specific feature elements #22

Closed
jbpros opened this issue Jul 27, 2011 · 9 comments
Closed

Target specific feature elements #22

jbpros opened this issue Jul 27, 2011 · 9 comments
Milestone

Comments

@jbpros
Copy link
Member

jbpros commented Jul 27, 2011

Only execute parts of a feature.

  • FILE:LINE syntax
  • --name
  • --lines

Some existing step definitions depend on this (e.g. When(/^Cucumber executes the scenario "([^"]*)"$/, ...);). Update them as soon as this is finished.

@stephanelpaul
Copy link

Shouldn't there be a --tags argument?

@jbpros
Copy link
Member Author

jbpros commented Feb 3, 2012

@stephanep Yes, see #7. It should be ready soon.

@jbpros
Copy link
Member Author

jbpros commented Jun 30, 2014

See #182 for more info.

@charlierudolph
Copy link
Member

@jbpros whats left here FILE:LINE is already supported. Is --name and --not-name the things that are wanted out of this?

@jbpros
Copy link
Member Author

jbpros commented Sep 28, 2015

@charlierudolph yep.

@jbpros
Copy link
Member Author

jbpros commented Oct 10, 2015

We're also missing the multiple line numbers (used by rerun, among other things):

features/hello_world.feature:21:34:46:88

@jbpros jbpros modified the milestones: ancillary features, 1.0 release Oct 10, 2015
@charlierudolph
Copy link
Member

cucumber-ruby has

-n, --name NAME

Only execute the feature elements which match part of the given name.
If this option is given more than once, it will match against all the
given names.

I don't think we need --no-name as least to start.

@jbpros
Copy link
Member Author

jbpros commented Oct 14, 2015

Nah, don't bother with --no-name.

@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
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants