-
Notifications
You must be signed in to change notification settings - Fork 36
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
Tries to run a Cucumber .feature with rspec #59
Comments
@trevordjones how did you get cucumber tests working? |
Hopefully this is just temporary - I ended up having to adjust my ruby-test settings so that my Rspec commands are mapped to Cucumber. Obviously it's inconvenient - if I wanted to then run Rspec tests, I have to switch it back over. I haven't heard of any progress on the issue yet. |
👍 Same issue here. |
Yep, if you read the code, there is no implementation of any settings other than the Rspec ones. Misleading documentation and settings 👎 |
It works for me. @travis-anderson: I don't follow you. |
(v 0.9.13) I uninstalled it, wiped the settings clean, reinstalled it and have the same problem. I've disabled all (non-core) packages with the same results. I've also tried all kinds of command line variations in the settings: I've also changed the rspec command line to " |
@moxley What is the command to run cucumber tests? It's possible that something is messing up in the framework detection because when I run the 'test-file' command with a .feature file open, it still runs my configured |
I don't know if I'm parsing it right, but it seems that, according to lib/source-info.coffee (line 114), ruby-test will run the test as rspec if the current project uses rspec... Except projects like the one I'm working with, which uses both rspec and cucumber. I think it should check filetype first, then project type (at least for single test runs). |
0ab0431 fixes the scenario where a cucumber file wasn't being detected when a |
Fixed! Thanks for chasing that down. |
When I'm viewing a .feature file and I run Ruby Test: Test File (or any other Ruby Test command) it tries to run the feature using rspec instead of cucumber.
The text was updated successfully, but these errors were encountered: