You can clone with
HTTPS or Subversion.
I followed the instructions in the README, and I'm getting the following output from guard-jasmine:
vagrant@lucid64:/vagrant$ guard-jasmine spec --verbose
18:24:48 - INFO - Guard::Jasmine starts Unicorn spec server on port 58713 in test environment (coverage off).
I, [2013-04-03T18:24:48.761952 #14423] INFO -- : listening on addr=0.0.0.0:58713 fd=7
I, [2013-04-03T18:24:48.762099 #14423] INFO -- : worker=0 spawning...
I, [2013-04-03T18:24:48.763095 #14423] INFO -- : master process ready
I, [2013-04-03T18:24:48.763589 #14428] INFO -- : worker=0 spawned pid=14428
I, [2013-04-03T18:24:48.763756 #14428] INFO -- : Refreshing Gem list
18:24:48 - INFO - Waiting for Jasmine test runner at http://localhost:58713/jasmine
I, [2013-04-03T18:24:53.874601 #14428] INFO -- : worker=0 ready
E, [2013-04-03T18:24:54.706076 #14428] ERROR -- : app error: No route matches [GET] "/jasmine" (ActionController::RoutingError)
I'm using the jasmine gem without the asset pipeline:
gem 'rails', '3.2.13'
group :test, :development do
gem "rspec-rails", "~> 2.0"
phantomjs is working with my capybara tests, so that's not the problem. I can also run my jasmine tests in a browser by running rake jasmine, so that's working too.
Is there a step missing in the README? Is there any setup I need to do, or is something broken in the gem?
Might be related to #102 and a missing release since then?
Okay, reading through a bunch of issues, it seems like I need to run guard-jasmine like this:
guard-jasmine spec --server=jasmine_gem
Sending a doc pull request in a second. It wasn't quite obvious from the README
Refactor default server option detection.
This refactoring moves the server detection before
the default Jasmine URL generation, since in case
of the Jasmine Gem as server, we want to have
`/` as runner url and not `/jasmine` like all the other
Fixes #120, Closes #121
Proper spec dir detection when using the Jasmine gem. (See #120)