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

Test​RSpec

by astrauka ST2/ST3

RSpec plugin for Sublime Text 3

Labels ruby, testing, rspec, spec

Details

Installs

  • Total 1K
  • Win 107
  • OS X 800
  • Linux 264
Jun 27 Jun 26 Jun 25 Jun 24 Jun 23 Jun 22 Jun 21 Jun 20 Jun 19 Jun 18 Jun 17 Jun 16 Jun 15 Jun 14 Jun 13 Jun 12 Jun 11 Jun 10 Jun 9 Jun 8 Jun 7 Jun 6 Jun 5 Jun 4 Jun 3 Jun 2 Jun 1 May 31 May 30 May 29 May 28 May 27 May 26 May 25 May 24 May 23 May 22 May 21 May 20 May 19 May 18 May 17 May 16 May 15 May 14
Windows 2 0 0 0 1 0 1 0 1 0 0 0 0 0 0 1 0 0 0 1 0 0 0 2 0 0 1 0 0 0 0 1 0 2 0 1 1 0 0 0 0 0 0 0 1
OS X 0 3 0 2 0 3 1 3 1 0 2 7 3 0 2 2 1 1 3 4 1 0 3 1 0 2 1 1 4 5 0 1 2 1 2 3 2 3 0 3 3 3 8 4 2
Linux 1 0 1 1 1 1 2 2 0 0 1 0 2 0 1 1 2 0 0 1 0 0 0 0 0 0 3 2 1 0 0 1 0 0 0 0 1 1 0 0 0 2 2 4 1

Readme

Source
raw.​githubusercontent.​com

Sublime TestRSpec

RSpec plugin for Sublime Text 3

Run, navigate and create specs from Sublime editor.

Features

Motivation

I have used RubyTest plugin for some time and was not happy with it.

So I decided to create a simple to understand and develop plugin targeting only rspec.

Installation

With Package Control:

  1. Run “Package Control: Install Package” command, find and install Test Rspec plugin.
  2. Restart SublimeText editor

Manually:

  1. Clone this git repository into your packages folder (in SublimeText, Preferences -> Browse Packages to open this folder)
  2. Restart SublimeText editor

Output

Executed using sublime build tools exec command.

When preconditions are not satisfied outputs to panel.

Configuration

Read this if you want to know how Sublime package settings work.

Find settings in “Preferences -> Package Settings -> TestRSpec”

Default settings

Key bindings

Find bindings in “Preferences -> Package Settings -> TestRSpec”

Default bindings

Features

Run rspec

Executes Sublime command to run rspec. Displays output in panel.

Launch rspec for: * current line * current file * run previous spec

Command generation

# output example
# /home/user/.rbenv/bin/rbenv exec bundle exec spring rspec /home/user/dev/project/spec/models/user_spec.rb:2
#
# ProjectRoot
#   project root by ../spec
#
# SpecTarget
#   file + line
#
# Rspec
#   Environment variables
#     take from configuration
#
#   (BinRspec || RubyRspec) + SpecTarget
#
#   BinRspec
#     find /bin/rspec from project root
#
#   on ./bin/rspec not found
#     RubyRspec : (Rbenv || Rvm || SystemRuby) + Bundle + Spring
#       Rbenv on configuration
#         find $HOME/.rbenv/bin/rbenv exec
#
#       Bundle on configuration
#         check if Gemfile is present
#         bundle exec
#
#       Spring on configuration
#         check if Gemfile contains spring
#         spring

Switch between code and test

Returns all matches by file name.

Prioritizes matches by path as they are more likely the right ones such that in most cases you pick the first match.

Create spec file

Creates spec file when launched in source file.

Uses code snippet defined in settings.

Troubleshooting

Ruby not found

Example error:

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

Update package settings with path to ruby, for rbenv that's:

"rspec_add_to_path": "$HOME/.rbenv/shims",

Acknowledgments

Inspired by https://github.com/maltize/sublime-text-2-ruby-tests

Parts that are taken: * test console theme * key bindings * idea of how to switch between code and test * idea of how to run spec

Contribution

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

Sublime Text plugin development links

Copyright and license

Copyright © 2016 @astrauka

Licensed under the MIT license.