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.
Not a big deal, I'll rename our directories but it does yield an error that left me scratching my head for a moment:
The directory in question is
features/auction management, the command being used to run isbundle exec rake "knapsack_pro:cucumber[--format junit --out test-reports/cucumber/junit.xml]"This is not the same behavior as running with
cucumber.