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

RubyTest fires unit test command instead of rspec #258

Open
dustinhansen opened this issue May 22, 2015 · 2 comments
Open

RubyTest fires unit test command instead of rspec #258

dustinhansen opened this issue May 22, 2015 · 2 comments

Comments

@dustinhansen
Copy link

I have an RSpec file open but when I try to run the tests (Cmd+Shift+T), I find that run_ruby_unit_command is getting used and not run_rspec_command. Why is this? I have another project that doesn't seem to have this problem. How does RubyTest identify which command to run?

@bglick
Copy link

bglick commented May 23, 2015

What's the name of your spec file? The file name is used and some of the name matching appears to have issues as reported in #243

I have a pull request in for this, but it has not been merged.

@dustinhansen
Copy link
Author

My file structure looks like this:

/data_science.sublime-project (my Sublime project file)
/splittest.rb
/spec/splittest_spec.rb

When I hit Cmd+Shift+T I can see the command being run is bundle exec ruby -Itest spec/splittest_spec.rb but it should run rspec.

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