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.

Sign up for GitHub

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

Jump to bottom

Run features/scenarios by name #233

Closed
aslakhellesoy opened this issue Mar 1, 2012 · 2 comments
Closed

Run features/scenarios by name #233

aslakhellesoy opened this issue Mar 1, 2012 · 2 comments
Assignees
@aslakhellesoy

Comments

@aslakhellesoy
Copy link
Contributor

There should be a --name "bla bla" option for running by name. This should also be available in @Cucumber.Options - see #160
@ghost ghost assigned aslakhellesoy Mar 1, 2012
@aslakhellesoy
Copy link
Contributor Author

Also see https://groups.google.com/d/topic/cukes/g30pLuacN-k/discussion - I do like an alternative way to specify this, via some.feature#Some Scenario

(This is similar to how cucumber-classic allows lines to be specified with --line 44 as well as some.feature:44 - which, by the way, we should support too.

@aslakhellesoy aslakhellesoy mentioned this issue Mar 1, 2012
Closed
klausbayrhammer added a commit to klausbayrhammer/cucumber-jvm that referenced this issue May 17, 2012
@klausbayrhammer
refs cucumber#233 run features/scenarios by name
76b1949 
added --name argument to specify a pattern to match a scenario or feature name
@klausbayrhammer klausbayrhammer mentioned this issue May 17, 2012
Merged
@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.
Assignees

@aslakhellesoy aslakhellesoy

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@aslakhellesoy