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

Doesn't work with feature directories with spaces #27

Closed
rosskevin opened this issue Mar 22, 2017 · 1 comment
Closed

Doesn't work with feature directories with spaces #27

rosskevin opened this issue Mar 22, 2017 · 1 comment

Comments

@rosskevin
Copy link

rosskevin commented Mar 22, 2017

Not a big deal, I'll rename our directories but it does yield an error that left me scratching my head for a moment:

I, [2017-03-22T17:01:22.143211 #1642]  INFO -- : [knapsack_pro] Test suite time execution recording enabled.
No such file or directory - features/auction. You can use `cucumber --init` to get started.
I, [2017-03-22T17:01:22.943221 #1642]  INFO -- : [knapsack_pro] No test files were executed on this CI node. When you use knapsack_pro regular mode then probably reason might be very narrowed tests list - you run only tests with specified tag and there are fewer test files with the tag than node total number.
I, [2017-03-22T17:01:23.286539 #1642]  INFO -- : [knapsack_pro] API request UUID: 7257ab85-d79c-469f-865e-22d94487163f
I, [2017-03-22T17:01:23.286757 #1642]  INFO -- : [knapsack_pro] API response:
I, [2017-03-22T17:01:23.286834 #1642]  INFO -- : [knapsack_pro] 
I, [2017-03-22T17:01:23.286864 #1642]  INFO -- : [knapsack_pro] Saved time execution report on API server.
I, [2017-03-22T17:01:23.286950 #1642]  INFO -- : [knapsack_pro] Global time execution for tests: 0s
Exited with code 2

The directory in question is features/auction management, the command being used to run is bundle exec rake "knapsack_pro:cucumber[--format junit --out test-reports/cucumber/junit.xml]"

This is not the same behavior as running with cucumber.

ArturT added a commit that referenced this issue Mar 22, 2017
@ArturT
Copy link
Member

ArturT commented Mar 22, 2017

Good catch! I've just fixed that and released a new gem version. Thanks for letting me know about the issue. :)

@ArturT ArturT closed this as completed Mar 22, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants