GithubHelp home page GithubHelp logo

atom-rspec's People

Contributors

diiq avatar fcoury avatar hansondr avatar jpemberthy avatar layonferreira avatar lehresman avatar matugm avatar povilasjurcys avatar superchris avatar vanboom avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar

atom-rspec's Issues

Maybe missing feature: run all rspec tests in directory

Hi there,

first of all thanks a lot for making it possible to run rspec test in Atom. Awesome!

I am not sure if there had been discussions about this already, but it would be very cool to have the possibility to run all the tests in the marked directory in the tree pane. In the end it would be possible to run all tests if one marks the directory spec.

Thanks and cheers

Andy

Package stopped working.

Really love this plugin, very recently though it has completely stopped working. Running my keyboard shortcuts does not do anything, neither running it through the palette. I have tried restarting and updating both Atom and atom-rspec. Any ideas what could be happening?

rspec:run-for-line not running the line of the cursor

I noticed that if I put my cursor on an it 'should do something' do line and run the 'rspec:run-for-line' command (using ctrl-alt-x) rspec seems to be given the line number for the line preceding the cursor. The screenshot shows an example:

screenshot 2014-03-24 18 10 06

The cursor is focused on line 201, which should mean that only one spec is run. Instead, line 200 is passed to rspec which runs the entire describe block containing 5 specs.

Uncaught TypeError: undefined is not a function

[Enter steps to reproduce below:]

  1. ...
  2. ...

Atom Version: 0.207.0
System: Mac OS X 10.10.3
Thrown From: rspec package, v0.3.1

Stack Trace

Uncaught TypeError: undefined is not a function

At /Users/jon/.dotfiles/atom.symlink/packages/rspec/lib/rspec-view.coffee:61

TypeError: undefined is not a function
  at RSpecView.module.exports.RSpecView.terminalClicked (/Users/jon/.dotfiles/atom.symlink/packages/rspec/lib/rspec-view.coffee:61:30)
  at HTMLPreElement.<anonymous> (/Users/jon/.dotfiles/atom.symlink/packages/rspec/lib/rspec-view.coffee:1:1)
  at HTMLPreElement.jQuery.event.dispatch (/Users/jon/.apps/Atom.app/Contents/Resources/app.asar/node_modules/jquery/dist/jquery.js:4435:9)
  at HTMLPreElement.elemData.handle (/Users/jon/.apps/Atom.app/Contents/Resources/app.asar/node_modules/jquery/dist/jquery.js:4121:28)

Commands

Config

{
  "core": {
    "ignoredNames": [
      ".bundle",
      ".git",
      "log",
      "repositories",
      "tmp",
      "vendor"
    ],
    "disabledPackages": [
      "exception-reporting",
      "metrics",
      "autocomplete",
      "linter-scss-lint",
      "atom-lint",
      "linter"
    ],
    "themes": [
      "unity-ui",
      "atom-light-syntax"
    ],
    "projectHome": "/Users/jon/Sites/"
  },
  "rspec": {
    "command": "spring rspec",
    "save_before_run": true,
    "force_colored_results": false
  }
}

Installed Packages

# User
atom-color-highlight, v3.0.9
autocomplete-ruby, v0.1.0
circle-ci, v0.10.0
color-picker, v2.0.4
coverage, v0.6.1
emmet, v2.3.10
file-icons, v1.5.7
jshint, v1.3.7
language-rspec, v0.3.0
linter-csslint, v0.0.13
linter-erb, v0.1.1
pretty-json, v0.3.3
project-manager, v1.15.10
react, v0.12.0
remote-atom, v1.2.6
rspec, v0.3.1
ruby-slim, v0.2.0
slack-chat, v1.0.1
unity-ui, v2.0.11

# Dev
No dev packages

Works fine, but inserts € into code

The runner works fine, but the commands add an extraneous € (or ≈) into the code: Looks like the key-mapping does not properly suppress the character. Is this an atom-issue, just a configuration I need to change somewhere?!

Package.activateConfig is deprecated.

Use a config schema instead. See the configuration section
of https://atom.io/docs/latest/hacking-atom-package-word-count and
https://atom.io/docs/api/latest/Config for more details

Package.activateConfig (/opt/atom/resources/app.asar/src/package.js:265:11)
PackageDetailView.activate (/opt/atom/resources/app.asar/node_modules/settings-view/lib/package-detail-view.js:163:26)
PackageDetailView.initialize (/opt/atom/resources/app.asar/node_modules/settings-view/lib/package-detail-view.js:146:12)
PackageDetailView.View (/opt/atom/resources/app.asar/node_modules/atom-space-pen-views/node_modules/space-pen/lib/space-pen.js:184:25)
new PackageDetailView (/opt/atom/resources/app.asar/node_modules/settings-view/lib/package-detail-view.js:38:54)
<unknown> (/opt/atom/resources/app.asar/node_modules/settings-view/lib/settings-view.js:256:22)

Issue where bundle exec seems to not be respected

My config:

'rspec':
  'command': 'bundle exec rspec'

Running Rspec: Run or Rspec: Run All:

/Users/pete/.gem/ruby/2.0.0/gems/bundler-1.6.2/lib/bundler/runtime.rb:34:in `block in setup': You have already activated rspec-core 2.14.7, but your Gemfile requires rspec-core 2.10.0. Prepending `bundle exec` to your command may solve this. (Gem::LoadError)

Using Chruby on OS X.

Not working with oh-my-zsh

I am using oh-my-zsh as my default shell. When I run this plugin in Atom, I saw this error message

/Users/jiamingz/.oh-my-zsh/oh-my-zsh.sh: line 12: autoload: command not found
/Users/jiamingz/.oh-my-zsh/oh-my-zsh.sh: line 31: syntax error near unexpected token `('
/Users/jiamingz/.oh-my-zsh/oh-my-zsh.sh: line 31: `for config_file ($ZSH/lib/*.zsh); do'
bash: line 1: undefined: command not found

bash: line 1: rspec: command not found

This thing used to work just fine with the following configuration:

'rspec':
  'command': 'bundle exec rspec'

But right now I get:

bash: line 1: rspec: command not found

Any ideas?

Changes the text background color

There's a weird behaviour when running the test. It's adding this black background color to the text.
I don't really know if this is the expected behaviour though.

rspec_error
rspec_error_1

Deprecated Atom APIs will be removed June 1st

Atom will no longer load this package after June 1st without changes. There are a couple deprecations on the latest version (0.3.0) of this package:

  1. The context menu CSON format has changed. Please see https://atom.io/docs/api/latest/ContextMenuManager#context-menu-cson-format for more info.
  2. Use activationCommands instead of activationEvents in your package.json Commands should be grouped by selector as follows: json "activationCommands": { "atom-workspace": ["foo:bar", "foo:baz"], "atom-text-editor": ["foo:quux"] }
  3. Use a config schema instead. See the configuration section of https://atom.io/docs/latest/hacking-atom-package-word-count and https://atom.io/docs/api/latest/Config for more details
  4. If you would like your pane item with class <ClassName> to support modified behavior, please implement a ::onDidChangeModified() method. If not, ignore this message. ::on methods for items are no longer supported.
  5. If you would like your pane item with class <ClassName> to support title change behavior, please implement a ::onDidChangeTitle() method. ::on methods for items are no longer supported. If not, ignore this message.
  6. The changeFocus option has been renamed to activatePane
  7. Use ::getPaths instead

Visit https://gist.github.com/benogle/6d09e295c84b717ef9b4 and search for your package name to see up-to-date deprecations.

If this package has been replaced by another package or functionality in core, please reply with this information.

See atom/atom#6867 for more info. Thanks!

Using Spork server causes output to be displayed on terminal instead of Atom window

For those who might use like me Spork server,

I managed to get back display on atom window using the following hack :

if Spork.using_spork?
  Spork.each_run do
    # This code will be run each time you run your specs.
    RSpec.configure do |config|
        config.reset
        config.output_stream = $stdout
    end
  end
end

to place in spec_helper.rb

And then, change atom-rspec command to

bundle exec rspec --drb

in atom preferences.

Failed to activate the rspec package

I cloned this repository directly in .atom/packages

  1. Move the cursor to it "...."
  2. Alt+Ctrl+T

Atom Version: 1.0.3
System: Mac OS X 10.10
Thrown From: rspec package, v0.3.3

Stack Trace

Failed to activate the rspec package

At Cannot find module 'atom-space-pen-views'

Error: Cannot find module 'atom-space-pen-views'
  at Module._resolveFilename (module.js:328:15)
  at Function.Module._resolveFilename (/Applications/Atom.app/Contents/Resources/app.asar/src/module-cache.js:383:52)
  at Function.Module._load (module.js:270:25)
  at Module.require (module.js:357:17)
  at require (module.js:376:17)
  at Object.<anonymous> (/Users/mac/.atom/packages/atom-rspec/lib/rspec-view.coffee:1:36)
  at Object.<anonymous> (/Users/mac/.atom/packages/atom-rspec/lib/rspec-view.coffee:1:1)
  at Module._compile (module.js:452:26)
  at Object.requireCoffeeScript (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/coffee-cash/lib/coffee-cash.js:85:19)
  at Module.load (module.js:347:32)
  at Function.Module._load (module.js:302:12)
  at Module.require (module.js:357:17)
  at require (module.js:376:17)
  at Object.<anonymous> (/Users/mac/.atom/packages/atom-rspec/lib/rspec.coffee:1:13)
  at Object.<anonymous> (/Users/mac/.atom/packages/atom-rspec/lib/rspec.coffee:1:1)
  at Module._compile (module.js:452:26)
  at Object.requireCoffeeScript (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/coffee-cash/lib/coffee-cash.js:85:19)
  at Module.load (module.js:347:32)
  at Function.Module._load (module.js:302:12)
  at Module.require (module.js:357:17)
  at require (module.js:376:17)
  at Package.module.exports.Package.requireMainModule (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:715:34)
  at Package.module.exports.Package.activateConfig (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:261:14)
  at Package.module.exports.Package.activateNow (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:239:14)
  at /Applications/Atom.app/Contents/Resources/app.asar/src/package.js:792:25
  at Emitter.module.exports.Emitter.emit (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/event-kit/lib/emitter.js:82:11)
  at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:222:20)
  at /Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:3:61
  at KeymapManager.module.exports.KeymapManager.dispatchCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:524:16)
  at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:347:22)
  at HTMLDocument.module.exports.WindowEventHandler.onKeydown (/Applications/Atom.app/Contents/Resources/app.asar/src/window-event-handler.js:177:20)

Commands

     -0:25.4.0 core:close (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
     -0:24.4.0 fuzzy-finder:toggle-file-finder (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
  6x -0:22.6.0 core:backspace (atom-text-editor.editor.mini.is-focused)
     -0:14.8.0 core:confirm (atom-text-editor.editor.mini.is-focused)
  2x -0:06.1.0 atom-terminal-panel:toggle-autocompletion (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
     -0:01.1.0 rspec:run (atom-text-editor.editor.vim-mode.normal-mode.is-focused)

Config

{
  "core": {}
}

Installed Packages

# User
atom-terminal-panel, v4.4.4
vim-mode, v0.57.0

# Dev
No dev packages

Windows CD (Change Directory) Error

When I try to run the command it tries to cd into my project directory but all the slashes are removed. So I get a directory not found, etc.

Package.getActivationCommands is deprecated.

Deprecated APIs will be removed on June 1st

Output from Atom:

Use activationCommands instead of activationEvents in your package.json
Commands should be grouped by selector as follows:

  "activationCommands": {
    "atom-workspace": ["foo:bar", "foo:baz"],
    "atom-text-editor": ["foo:quux"]
  }
Package.getActivationCommands (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:808:9)
Package.hasActivationCommands (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:733:20)
<unknown> (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:185:24)
Package.measure (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:163:15)
Package.load (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:177:12)
PackageManager.loadPackage (/Applications/Atom.app/Contents/Resources/app.asar/src/package-manager.js:355:14)

Added flexibility when creating the command to be run?

I've got my dev environment set up using Vagrant, and would love to have the ability to trigger rspec using this package.

I can run a spec from my host machine using something like the following in my terminal:

vagrant ssh -c 'rspec </path/to/spec>'

Unfortunately I'm not able to build this command using the package. I think the problem would be solved if some variable containing the spec path was exposed and could be used in the "Command" setting, in stead of being appended after what's in that setting.

Running run-last-test after run-for-line always fails

Try this: hit ctrl-alt-x then ctrl-alt-e. The rspec output window says:

RSpec - range_fixes_spec.rb
RSpec - spec
/Users/bronson/.gem/ruby/2.2.2/gems/rspec-core-3.4.1/lib/rspec/core/configuration.rb:1361:in `load': cannot load such file -- /Users/bronson/invoicing/spec (LoadError)
    from /Users/bronson/.gem/ruby/2.2.2/gems/rspec-core-3.4.1/lib/rspec/core/configuration.rb:1361:in `block in load_spec_files'
    from /Users/bronson/.gem/ruby/2.2.2/gems/rspec-core-3.4.1/lib/rspec/core/configuration.rb:1359:in `each'
    from /Users/bronson/.gem/ruby/2.2.2/gems/rspec-core-3.4.1/lib/rspec/core/configuration.rb:1359:in `load_spec_files'
    from /Users/bronson/.gem/ruby/2.2.2/gems/rspec-core-3.4.1/lib/rspec/core/runner.rb:102:in `setup'
    from /Users/bronson/.gem/ruby/2.2.2/gems/rspec-core-3.4.1/lib/rspec/core/runner.rb:88:in `run'
    from /Users/bronson/.gem/ruby/2.2.2/gems/rspec-core-3.4.1/lib/rspec/core/runner.rb:73:in `run'
    from /Users/bronson/.gem/ruby/2.2.2/gems/rspec-core-3.4.1/lib/rspec/core/runner.rb:41:in `invoke'
    from /Users/bronson/.gem/ruby/2.2.2/gems/rspec-core-3.4.1/exe/rspec:4:in `<top (required)>'
    from /Users/bronson/.gem/ruby/2.2.2/bin/rspec:23:in `load'
    from /Users/bronson/.gem/ruby/2.2.2/bin/rspec:23:in `<main>'

If you hit either ctrl-alt-t or ctrl-alt-r, and then ctrl-alt-e, everything works fine. It's just ctrl-alt-x that breaks things.

Run spec from code file

I'd like to be able to press the hotkey for "run test" from the code that I'm writing (not the spec file), and have it run the related test for that code.

Eg: if I'm working in dog.rb, I'd like to able to run dog_spec.rb (which could complete to spec/dog_spec.rb, or maybe ../../spec/models/dog_spec.rb).

Atom.Object.defineProperty.get is deprecated.

atom.workspaceView is no longer available.
In most cases you will not need the view. See the Workspace docs for
alternatives: https://atom.io/docs/api/latest/Workspace.
If you do need the view, please use atom.views.getView(atom.workspace),
which returns an HTMLElement.

Atom.Object.defineProperty.get (/Applications/Atom.app/Contents/Resources/app/src/atom.js:54:11)
Object.activate (/Users/ahmet/.atom/packages/rspec/lib/rspec.coffee:21:9)

Configuration weirdness

There's some weirdness how the configuration gets written and used. To recreate:

  1. Edit your config.cson. Remove anything related to 'rspec' or 'atom-rspec'. Save.
  2. Go into the settings UI for Atom Rspec. Change the command to "foo".
  3. Go back to config.cson. It now has configuration settings for both "rspec" and "atom-rspec", and they're different from each other.
  4. Run a spec. It runs whatever was in the "rspec" configuration, not what was in "atom-rspec".
  5. Changing the setting in the settings UI only changes the configuration for "atom-rspec", but it doesn't get picked up by the package.

Is this a bug in Atom? Or atom-rspec? I can't figure it out.

stty: stdin isn't a terminal

Hi there,

I'm getting the following output when I try to run cmd+alt+x in an rspec file (just installed atom-rspec). This is after restarting atom.

RSpec - interview_spec.rb
stty: stdin isn't a terminal
stty: stdin isn't a terminal
bash: line 1: undefined: command not found

Any ideas?

Thanks!

bundle exec

I'm not sure how you'd like to support it but I added a "bundle exec" prefix to my version. It seems like making the rspec command configurable would be a nice feature.

Maintainer seems MIA

Just throwing this out that someone who can give a little time to maintain this project should fork this repo and put it out on the Atom package site. Personally, I'm not that person right now, but someone out there might be able to.

Alternatively, the maintainer could add some collaborators to the repo. That assumes he ever comes back to this repo :-o

Uncaught TypeError: deprecationSite.getFileName is not a function

To reproduce:

  1. Open a Spec
  2. Go to Menu > Packages > RSpec > Run Current Spec

Atom Version: 1.2.0
System: Mac OS X 10.11
Thrown From: rspec package, v0.3.2

Stack Trace

Uncaught TypeError: deprecationSite.getFileName is not a function

At /Applications/Atom.app/Contents/Resources/app.asar/node_modules/grim/lib/grim.js:56

TypeError: deprecationSite.getFileName is not a function
  at Object.global.__grim__.deprecate (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/grim/lib/grim.js:56:36)
  at Object.jQuery.event.add (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/atom-space-pen-views/node_modules/space-pen/lib/space-pen.js:592:14)
  at space-pen-div.<anonymous> (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/jquery/dist/jquery.js:4861:17)
  at Function.jQuery.extend.each (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/jquery/dist/jquery.js:374:23)
  at RSpecView.jQuery.fn.jQuery.each (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/jquery/dist/jquery.js:139:17)
  at RSpecView.jQuery.fn.extend.on (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/jquery/dist/jquery.js:4860:15)
  at RSpecView.jQuery.fn.extend.on (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/jquery/dist/jquery.js:4823:10)
  at RSpecView.module.exports.RSpecView.initialize (/Users/pedrolucasp/.atom/packages/rspec/lib/rspec-view.coffee:20:6)
  at RSpecView.View [as constructor] (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/atom-space-pen-views/node_modules/space-pen/lib/space-pen.js:184:25)
  at RSpecView.ScrollView [as constructor] (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/atom-space-pen-views/lib/scroll-view.js:12:47)
  at new RSpecView (/Users/pedrolucasp/.atom/packages/rspec/lib/rspec-view.coffee:23:5)
  at /Users/pedrolucasp/.atom/packages/rspec/lib/rspec.coffee:39:11
  at Workspace.module.exports.Workspace.openURIInPane (/Applications/Atom.app/Contents/Resources/app.asar/src/workspace.js:454:22)
  at Workspace.module.exports.Workspace.open (/Applications/Atom.app/Contents/Resources/app.asar/src/workspace.js:393:19)
  at Object.module.exports.openUriFor (/Users/pedrolucasp/.atom/packages/rspec/lib/rspec.coffee:57:20)
  at Object.module.exports.runForLine (/Users/pedrolucasp/.atom/packages/rspec/lib/rspec.coffee:73:6)
  at atom-workspace.atom.commands.add.rspec:run-for-line (/Users/pedrolucasp/.atom/packages/rspec/lib/rspec.coffee:28:10)
  at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:260:29)
  at CommandRegistry.handleCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:3:61)
  at CommandRegistry.module.exports.CommandRegistry.dispatch (/Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:160:19)
  at AtomEnvironment.module.exports.AtomEnvironment.dispatchApplicationMenuCommand (/Applications/Atom.app/Contents/Resources/app.asar/src/atom-environment.js:984:28)
  at emitOne (events.js:77:13)
  at EventEmitter.emit (events.js:169:7)

Commands

     -2:34.8.0 core:save (atom-text-editor.editor.is-focused)
     -2:32.6.0 core:move-down (atom-text-editor.editor.is-focused)
     -2:32.1.0 core:backspace (atom-text-editor.editor.is-focused)
  2x -2:31.9.0 core:save (atom-text-editor.editor.is-focused)
     -2:15.5.0 editor:move-line-down (atom-text-editor.editor.is-focused)
     -2:14.9.0 core:move-up (atom-text-editor.editor.is-focused)
     -2:14.6.0 editor:move-to-end-of-screen-line (atom-text-editor.editor.is-focused)
  2x -2:13.8.0 core:save (atom-text-editor.editor.is-focused)
     -1:53.8.0 settings-view:check-for-package-updates (atom-text-editor.editor.is-focused)
     -1:12.8.0 editor:move-to-beginning-of-word (atom-text-editor.editor.is-focused)
  7x -1:12.5.0 core:move-left (atom-text-editor.editor.is-focused)
     -1:10.4.0 emmet:insert-formatted-line-break-only (atom-text-editor.editor.is-focused.autocomplete-active)
     -1:10.3.0 autocomplete-plus:confirm (atom-text-editor.editor.is-focused.autocomplete-active)
  2x -1:09.6.0 core:save (atom-text-editor.editor.is-focused)
     -0:59.2.0 core:confirm (atom-text-editor.editor.mini.is-focused)
     -0:01.9.0 rspec:run-for-line (atom-text-editor.editor.is-focused)

Config

{
  "core": {}
}

Installed Packages

# User
color-picker, v2.0.13
emmet, v2.3.14
nuclide-hack, v0.0.32
rspec, v0.3.2

# Dev
No dev packages

Marry atom-rspec with atom-rspec-focus to support running specific specs?

I currently use traviskroberts/atom-rspec-focus to mark specific specs I’d like to run with the tag focus. Regular execution would then be rspec spec/ --tag focus.

In general, it would be nice if this project supported a way of only executing specs of a certain tag. Merging atom-rspec-focus into this project combined with a new keyboard shortcut to only execute the specs marked with the tag focus seems like a possible way to do it.

[RSpec] exit with code: 127

having this log in console trying to run rspec, and my message is "rspec: command not found"

if it helps, im using rbenv

my bashrc:

export PATH="$HOME/.rbenv/bin:$PATH"
eval "$(rbenv init -)"
export PATH="$HOME/.rbenv/plugins/ruby-build/bin:$PATH"

works fine from terminal

rbenv support

It seems that atom-rspec use the OS X ruby installed by default, I got:

/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:45:in `require': cannot load such file -- bundler/setup (LoadError)   from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:45:in `require'  from bin/rspec:6:in `'

Ruby object outputs are show with file link

atom-rspec is thinking that something like #<Order:0x00000008327640> is a file, because ends with :0. It happens to be a very common case on ruby, so maybe we can fix this one?

This mistake is on the addOutput method.

A dummy fix for this other small issue would be adding allowed terminators after the number on the regexp, like /([^\s]*:[0-9]+(\s|\.|:))/g. Maybe you can think on something better than this?

Support spaces in the current path / No such file or directory error

atom-rspec v0.3.2
rspec:run command gives this error:

/Users/avk/.rvm/scripts/extras/bash_zsh_support/chpwd/function.sh: line 5: cd: /Users/avk/Documents/My: No such file or directory

I imagine it's because my current directory has spaces in the path:
~/Documents/My Work/The Right Margin/code/therightmargin

Can you please support spaces or escape them in paths?

Run all specs?

I'd love to run all specs via the same interface that I run one spec or a file's-worth.

There would need to be some way of pointing out which directory in the project contains the specs.

can't run specs - couldn't find HOME environment -- expanding `~' (ArgumentError)

this is the error i get when i try to run my specs from atom.
Running from command line (zsh + rbenv) works just fine.

WARNING: Unable to find /.rspec because the HOME environment variable is not set. Called from /usr/local/opt/rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/rspec-core-3.2.3/exe/rspec:4:in <top (required)>'. /usr/local/opt/rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/yard-0.8.7.6/lib/yard.rb:11:inexpand_path': couldn't find HOME environment -- expanding `' (ArgumentError)

Work with Pry.

Not sure what would be involved here, but it would be fantastic if the plugin supported using the Pry gem in tests. Currently trigger a binding.pry debug call results in crashing the plugin. At the moment I am swapping out to terminal to run tests when I need to debug with Pry.

Uncaught TypeError: undefined is not a function

[Enter steps to reproduce below:]

  1. Get a test to fail.
  2. Click on the link to open the failing test's spec file.
  3. Error!

Atom Version: 0.207.0
System: Mac OS X 10.10.3
Thrown From: rspec package, v0.3.1

Stack Trace

Uncaught TypeError: undefined is not a function

At /Users/jon/.dotfiles/atom.symlink/packages/rspec/lib/rspec-view.coffee:61

TypeError: undefined is not a function
  at RSpecView.module.exports.RSpecView.terminalClicked (/Users/jon/.dotfiles/atom.symlink/packages/rspec/lib/rspec-view.coffee:61:30)
  at HTMLPreElement.<anonymous> (/Users/jon/.dotfiles/atom.symlink/packages/rspec/lib/rspec-view.coffee:1:1)
  at HTMLPreElement.jQuery.event.dispatch (/Users/jon/.apps/Atom.app/Contents/Resources/app.asar/node_modules/jquery/dist/jquery.js:4435:9)
  at HTMLPreElement.elemData.handle (/Users/jon/.apps/Atom.app/Contents/Resources/app.asar/node_modules/jquery/dist/jquery.js:4121:28)

Commands

Config

{
  "core": {
    "ignoredNames": [
      ".bundle",
      ".git",
      "log",
      "repositories",
      "tmp",
      "vendor"
    ],
    "disabledPackages": [
      "exception-reporting",
      "metrics",
      "autocomplete",
      "linter-scss-lint",
      "atom-lint",
      "linter"
    ],
    "themes": [
      "unity-ui",
      "atom-light-syntax"
    ],
    "projectHome": "/Users/jon/Sites/"
  },
  "rspec": {
    "command": "spring rspec",
    "save_before_run": true,
    "force_colored_results": false
  }
}

Installed Packages

# User
atom-color-highlight, v3.0.9
autocomplete-ruby, v0.1.0
circle-ci, v0.10.0
color-picker, v2.0.4
coverage, v0.6.1
emmet, v2.3.10
file-icons, v1.5.7
jshint, v1.3.7
language-rspec, v0.3.0
linter-csslint, v0.0.13
linter-erb, v0.1.1
pretty-json, v0.3.3
project-manager, v1.15.10
react, v0.12.0
remote-atom, v1.2.6
rspec, v0.3.1
ruby-slim, v0.2.0
slack-chat, v1.0.1
unity-ui, v2.0.11

# Dev
No dev packages

Spinner spins indefinitely

When I try to run this (ctrl-alt-x and ctrl-alt-t both have this issue), the "starting rspec" shows up and hangs forever. No error messages in the console and I added some debug statements. It seems no data or errors come out of the terminal...as if you're not sending anything to it at all.

Atom verison 1.1.0
rspec version 3.3.2
atom-rspec version 0.3.2

Open rspec output in new tab

It would be much more fun to have rspec output in separate tab. That will allow user so put it where he wants: split horizontally, vertically or leave it hidden in one of opened tabs.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.