browser not loading specs / assets about jasmine-rails

[gerad]

Ok, as far as I can tell, the root cause is that process_require_jasmine_directive is not getting called by sprockets.

[gerad]

possibly due to tilt caching?

[gerad]

ok, so, as far as I can tell, the issue is that sprockets does not know to re-run require_jasmine in jasmine_rails/application.js due to additions to the files implicitly referenced in jasmine.yml

hence, if i've got a cached version of jasmine_rails/application.js around, then any specs I add are not going to be found and run

I'm not sure if there's a simple solution, as sprockets and jasmine.yml specify files to include in entirely different ways

my first instinct would be to ignore the explicit enumeration of src files in jasmine.yml and instead have the jasmine_rails rails engine just bring in application.js... this should be more true to production anyway

I'm not sure how that might affect the headless runner though

[gerad]

part of the problem is that the rails cache in development is filestore by default now

[searls]

I believe this is fixed. If not from the referenced pull request, then from the rewrite to how jasmine-rails searches for files.

[ryandoherty]

Just ran into this issue myself. Had to rm -rf tmp/cache/assets/* .

jasmine-core (1.3.1)
jasmine-rails (0.4.2)
rails (3.2.12)

[searls]

I just spent a little while trying to replicate, @ryandoherty and I was not able to -- could you push a minimal sample project to demonstrate?

[ryandoherty]

Quick question, is there anything in tmp/cache/assets? I will try to replicate but I think I did asset compilation at some point before setting up jasmine-rails and that was what caused the problem. Currently on a plane for vacation so I might not have time for ~1 week. Thanks!