ctrl+shift+p filters: :st2 :st3 :win :osx :linux
Browse

Test​RSpec

by astrauka ALL

RSpec plugin for Sublime Text 3

Labels ruby, testing, rspec, spec

Details

  • 2.1.0
  • github.​com
  • github.​com
  • 10 months ago
  • 51 minutes ago
  • 6 years ago

Installs

  • Total 4K
  • Win 455
  • Mac 3K
  • Linux 813
May 16 May 15 May 14 May 13 May 12 May 11 May 10 May 9 May 8 May 7 May 6 May 5 May 4 May 3 May 2 May 1 Apr 30 Apr 29 Apr 28 Apr 27 Apr 26 Apr 25 Apr 24 Apr 23 Apr 22 Apr 21 Apr 20 Apr 19 Apr 18 Apr 17 Apr 16 Apr 15 Apr 14 Apr 13 Apr 12 Apr 11 Apr 10 Apr 9 Apr 8 Apr 7 Apr 6 Apr 5 Apr 4 Apr 3 Apr 2 Apr 1
Windows 1 1 0 0 0 0 1 0 0 0 0 1 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 2 1 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0
Mac 0 0 0 0 2 0 0 0 0 1 1 1 0 0 2 1 0 0 1 1 1 0 0 0 2 0 1 0 1 0 0 0 0 0 1 1 0 1 1 1 2 0 0 0 1 2
Linux 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0

Readme

Source
raw.​githubusercontent.​com

Sublime TestRSpec

RSpec plugin for Sublime Text 3.

Run, navigate and create specs from Sublime Text.

Features

Installation

Using Package Control:

  1. Run “Package Control: Install Package” command, find and install TestRspec.
  2. Define key bindings (see Configuration section below).
  3. Restart Sublime Text.

Manually:

  1. Clone this repository into your packages folder (in Sublime Text: Preferences -> Browse Packages).
  2. Define key bindings (see Configuration section below).
  3. Restart Sublime Text.

Configuration

TestRSpec tries its best to autodetect how to run RSpec. However, you might need to make adjustments to plugin's configuration if you have an uncommon setup.

There are no key bindings enabled by default. Go to Preferences -> Package Settings -> TestRSpec -> Key Bindings to define key bindings.

Find settings in Preferences -> Package Settings -> TestRSpec.

Default settings

Features

Run RSpec

Launch RSpec for:

  • Current file
  • Current line
  • Rerun last run spec

Switch between code and spec

Jumps from code to spec and vice versa. If there multiple matches, it shows a list with matches.

Create a spec file

Creates a spec file when run in a source file.

Uses code snippet defined in settings (create_spec_snippet).

Copy last ran RSpec command

Copies the command of the last run spec. It can be useful e.g. when you want to debug your application within a 'real' terminal.

Tips

Ignore binding.pry when running specs

Sublime does not allow input in the output panel, so if you add binding.pry, tests get stuck waiting on input.

To work around this, you can disable the debugger by modifying TestRSpec configuration:

{
  "env": {
    "DISABLE_PRY": "true"
  }
}

Alternatively, use pry-remote.

Troubleshooting

Ruby not found or wrong ruby version used

Example error:

/usr/bin/env: ruby: No such file or directory

Override PATH variable in your shell configuration (~/.bashrc or ~/.bash_profile). Make sure ruby command runs the right Ruby version in bash.

Alternatively, update package settings with path to ruby, e.g.:

{
  "rspec_add_to_path": "$HOME/.rbenv/shims"
}

Spring is not used

Make sure you have both spring and spring-commands-rspec in your Gemfile.

If you use binstubs, you also need to run

bundle exec spring binstub rspec

Acknowledgments

Inspired by and uses code from https://github.com/maltize/sublime-text-2-ruby-tests

Contribution

Help is always welcome. Create an issue if you need help.

Copyright and license

Copyright © 2016 @astrauka

Licensed under the MIT license.