rake spec:javascript(s) do not exist about jasmine-rails

[searls]

sounds legit -- I didn't run into this in local testing but it's probably because of how I'd been loading the gem.

[pschuegr]

Ah. If you have a sec, can you outline how you load the gem? I'm also having troubles importing the rake tasks manually, although I'm pretty sure that's just something dumb that I'm doing right now.

[searls]

I just did this and the rake task appeared (it blew up because I didn't define a jasmine.yml file, but that's not the task's fault per se):

$ rails new bar
$ cd bar

Then added this to Gemfile:

group :development, :test do
  gem 'jasmine-rails'
end

Then

$ bundle
$ bundle exec rake spec:javascript

And I got this expected explosion:

No such file or directory - /Users/justin/tmp/bar/spec/javascripts/support/jasmine.yml
/Users/justin/tmp/bar/config/environment.rb:5:in `<top (required)>'
Tasks: TOP => spec:javascript => environment
(See full trace by running task with --trace)

[searls]

I'll close this for now -- if you post an example app demonstrating the issue, we can reopen it.

[pschuegr]

I'm not sure how this works on your system - I did essentially the same thing:

https://gist.github.com/pschuegr/5462006

And get what I expected - it doesn't know anything about rake spec:javascript. Do you have some kind of system wide change?

[searls]

Thanks for sharing your output!

You're not seeing the rake task b/c you're on [email protected] and the rake task was introduced in 0.4.0. (Current version is 0.4.2)

[pschuegr]

Ok - so the last version available on rubygems is 0.3.2 then - I guess we need to point to the github version.

Thanks for looking at this.

[searls]

Actually, it is on Rubygems.

http://rubygems.org/gems/jasmine-rails

I imagine you probably have locked to an older version. Ensure you're not specifying a version and then bundle update the gem.

On Apr 25, 2013, at 6:39 PM, Paul Schuegraf [email protected] wrote:

Ok - so the last version available on rubygems is 0.3.2 then - I guess we need to point to the github version.

Thanks for looking at this.

�
Reply to this email directly or view it on GitHub.