Create an account

Very important

  • To access the important data of the forums, you must be active in each forum and especially in the leaks and database leaks section, send data and after sending the data and activity, data and important content will be opened and visible for you.
  • You will only see chat messages from people who are at or below your level.
  • More than 500,000 database leaks and millions of account leaks are waiting for you, so access and view with more activity.
  • Many important data are inactive and inaccessible for you, so open them with activity. (This will be done automatically)


Thread Rating:
  • 974 Vote(s) - 3.47 Average
  • 1
  • 2
  • 3
  • 4
  • 5
RubyTest in Sublime Text 2

#1
I am trying to get [RubyTest][1] to work in Sublime Text 2. I followed the Instruction on the Github Readme and get the following error. Does anyone know how I could fix this?

/bin/sh: rspec: command not found

[1]:

[To see links please register here]

Reply

#2
To get this to work you only need to change one setting in the RubyTest package in sb2.

If you are using rvm, your rspec gem is installed through rvm and is not found in /bin/sh

So you need to set the RubyTest package for Sublime Text 2 to automatically check for your rvm environment variables.


What to change:

1) In Sublime Text 2, go to Preferences|Browse Packages. This will open up your packages directory.

2) Open the 'RubyTest' directory and look for the file 'RubyTest.sublime-settings'.

3) find the line that says:

"check_for_rvm": false,

and change it to:

"check_for_rvm": true,
save the change.

4) That's it. It should now work.

Good Luck
Reply

#3
I spent many hours struggling with this same problem! I could not get rspec to run within Sublime Text 2, using the Michael Hartl "Ruby on Rails Tutorial." It kept saying:

/bin/sh: rspec: command not found

I finally realized that the RubyTest package (

[To see links please register here]

) was looking in the WRONG PLACE for my RVM!

On my Mac, the path for RubyTest is `/Library/Application Support/Sublime Text 2/Packages/Ruby Test`

First, to make RubyTest seek the RVM, I changed the parameter in RubyTest.sublime-settings from

"check_for_rvm": false, to "check_for_rvm": true,

Then I dug into the Python code of run_ruby_test.py:

[To see links please register here]


At line 151, inside class BaseRubyTask, it had the wrong path for my RVM:

rvm_cmd = os.path.expanduser('~/.rvm/bin/rvm-auto-ruby')

I changed it to the full correct path: `rvm_cmd = os.path.expanduser('/usr/local/rvm/bin/rvm-auto-ruby')`

If this is not your path, find the correct path by typing

`$ which rvm-auto-ruby` and substitute that instead.

After saving run_ruby_test.py, I went to Terminal, cd to my Rails application directory, and ran `spork`

Finally, I opened static_pages_spec.rb in Sublime Text 2. Now all the tests work from it!
Reply

#4
I'm using rbenv and found that adding the following to my .bashrc did the trick

/Users/user/.rbenv/shims/rspec
Reply

#5
No, you don't need to change paths, run sublime from command line etc.
If you are using RVM, you only have to do this:

Go to Sublime Text 2, go to
preferances-> package settings -> RubyTests

and pick settings-user or settings-default (depending what you are using) and change line:

"run_rspec_command": "rspec {relative_path}"
to

"run_rspec_command": "bundle exec rspec {relative_path}"

And so forth - add **bundle exec** to all commands

![enter image description here][1]


[1]:
Reply

#6
The following steps worked for me (I encountered the same error as OP):

1. Install the RubyTest plugin through the package control manager.
Note* If you don't have the package manager installed - I highly recommend it for managing sublime plugins - more info [here][1].

2. Be sure to add the [code here][2] to your RubyTest.sublime-settings file.
This file can be found at (from the menu): `Preferences -> Package settings -> RubyTest -> Settings User`

3. Save file, close Sublime and restart Sublime from the terminal in your project's folder using (so PATH is available in Sublime): `subl .`


[1]:

[To see links please register here]

[2]:

[To see links please register here]

-settings
Reply

#7
I had the same problem after installing RubyTest by cloning from the repo. I simply uninstalled and reinstalled the package inside Sublime using Package Control, then everything worked fine.
Reply

#8
This worked for me:

If you're using RVM, open a project with command line from the project's folder:

subl .

Then, it'll hook the ruby version and gems.
Reply

#9
You can see a summary of this issue here:

[To see links please register here]


Essentially, what Jim said was correct, you're running RVM or some other ruby vm manager that similarly monkeys with your PATH. Following the directions from this issue I did the following:

Install the binaries in my project

bundle install --binstubs

Add the path to my .bashrc and source it

echo 'export PATH="./bin:$PATH"' >> ~/.bashrc
source ~/.bashrc

Open the sublime project from the command line (so that PATH is available in Sublime Text 2)

subl .
Reply

#10
Running Sublime Text 2(2165) with RubyTest plugin. Ruby and Gems managed with rbenv (0.3.0).

First attempt to use RubyTest gave the following error:
`/bin/sh: rspec: command not found`

From the command line I ran
`which rspec`
and it returned no results.

After some digging, I read that `bundle install` does not put the executables in your $PATH.
[Alternative executable paths not picked up by shims sometimes][1]


In order to use the executible outside the app, I had to delete the gem installed by bundler and then install it manually.

`gem uninstall rspec`

`gem install rspec`

followed by

`rbenv rehash` (*Note* you will need to run `bundle` inside your app so it updates the location of the gem)

This had to be performed for each version of ruby I have under rbenv control.

Now when I run

`which rspec`

it is found in the path and RubyTest is able to grab it without any problems.

fwiw, I had to repeat the steps for cucumber as well. To use all of RubyTests' features, ruby, cucumber and rspec executables need to be in your $PATH (for rbenv it is `~/.rbenv/shims/`).


[1]:

[To see links please register here]

Reply



Forum Jump:


Users browsing this thread:
1 Guest(s)

©0Day  2016 - 2023 | All Rights Reserved.  Made with    for the community. Connected through