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

Tries to run a Cucumber .feature with rspec #59

Closed
etlund opened this issue Jun 21, 2015 · 10 comments
Closed

Tries to run a Cucumber .feature with rspec #59

etlund opened this issue Jun 21, 2015 · 10 comments

Comments

@etlund
Copy link

etlund commented Jun 21, 2015

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.

@esparkman
Copy link

@trevordjones how did you get cucumber tests working?

@trevordjones
Copy link

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.

@JonCrawford
Copy link

👍 Same issue here.

@travis-anderson
Copy link

Yep, if you read the code, there is no implementation of any settings other than the Rspec ones. Misleading documentation and settings 👎

@moxley
Copy link
Owner

moxley commented Aug 30, 2015

cucumber-sample

It works for me.

@travis-anderson: I don't follow you.

@etlund
Copy link
Author

etlund commented Aug 31, 2015

(v 0.9.13)
I am still not able to get it to run cucumber features. When I open a .feature file and run "Ruby Test: Test File" (or any of the other commands), it tries "Running test: rspec --tty features/homepage.feature" and blows up.

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:
bundle exec cucumber --color {relative_path}
spring cucumber --color {relative_path}
bin/cucumber --color {relative_path}

I've also changed the rspec command line to "cucumber --color {relative_path}" and it still tries to run a feature file by calling "rspec --tty features/homepage.feature"

@travis-anderson
Copy link

@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 Rspec File Command

@wendelscardua
Copy link

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).

moxley pushed a commit that referenced this issue Sep 11, 2015
@moxley
Copy link
Owner

moxley commented Sep 11, 2015

0ab0431 fixes the scenario where a cucumber file wasn't being detected when a .rspec file is in the project. Thanks for your contribution to ruby-test!

@etlund
Copy link
Author

etlund commented Sep 11, 2015

Fixed! Thanks for chasing that down.

@etlund etlund closed this as completed Sep 11, 2015
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

7 participants