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

Main not checking for empty feature paths #163

Closed
jvans opened this issue Jan 22, 2012 · 3 comments
Closed

Main not checking for empty feature paths #163

jvans opened this issue Jan 22, 2012 · 3 comments
Milestone
1.0.0

Comments

@jvans
Copy link

jvans commented Jan 22, 2012

No feedback is provided to users if no feature path is specified when running Main, which makes it hard to discern why no tests were run.
@aslakhellesoy
Copy link
Contributor

Classic cucumber will default to run ./features, but this is probably not a good default in JVM land, as features may be in a lot of different places, depending on the project.

I agree we should just raise an error with an explanation.

@aslakhellesoy
Copy link
Contributor

Fixed by 287bf9b

vladimirkl pushed a commit to vladimirkl/cucumber-jvm that referenced this issue Feb 9, 2012
@aslakhellesoy
Fail if no features are found. Closes cucumber#163
287bf9b
@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
No one assigned
Labels
None yet
Projects
None yet
Milestone
1.0.0
Development

No branches or pull requests
2 participants
@aslakhellesoy @jvans