search

testdouble / jasmine-rails

A Jasmine runner for rails projects that's got you covered in both the terminal and the browser
http://rubygems.org/gems/jasmine-rails
MIT License
378 stars 154 forks source link

Slow test runs with large apps #148

Closed rymohr closed 9 years ago

rymohr commented 9 years ago

Is there any way to force the javascript_include_tag to use debug: false to speed up test runs? Our specs depend on more than 1000 js files now and requesting each one separately is painfully slow.

searls commented 9 years ago

I'm not sure. Could you look into an asset pipeline setting?

You could add ?debug_assets=false to the URL for example

On Thu, Oct 23, 2014 at 7:30 PM, Ryan Mohr notifications@github.com wrote:

Is there any way to force the javascript_include_tag to use debug: false to speed up test runs? Our specs depend on more than 1000 js files now and requesting each one separately is painfully slow.

Reply to this email directly or view it on GitHub: https://github.com/searls/jasmine-rails/issues/148

rymohr commented 9 years ago

Thanks for the suggestion but it looks like that option was removed in rails 4:

http://guides.rubyonrails.org/asset_pipeline.html#turning-debugging-off http://apidock.com/rails/v3.2.3/Sprockets/Helpers/RailsHelper/debug_assets%3F

For now we've just disabled asset debugging entirely in development.

searls commented 9 years ago

hmm. one idea might be to flip it with an environment variable? Obviously debugging assets is very useful in the event you're, you know, actually debugging something