如何加速资产编译测试？

Question

Running Guard with Spin works great to keep my testing fast, except when assets are relevant and need compiling. It seems that the test environments recompiles all assets whenever I change something in them. I've seen examples of deployment scripts that only recompile assets whose source has changed. Can this be done for testing too? Or is there another way to speed up asset compilation for tests?

I'm using a rather specific setup so I'll be happy to supply more information if needed, though I feel the answer from this question might be of use in many more cases than just mine.

Answer 1

You can take a look at this article written two months ago . It seems rather complex task . Nathan has written a gem that precompiles only changes , made to assets . It can be used in development and testing env.

EDIT : Here is another article , related with speeding up our tests . It has a different point of view about js testing .

Answer 2

You can for example avoid adding require_tree in Your application js and css files.

In addition, use proper file extensions - if something is js - then name it like normal js files. Same for css and scss.

You can also precompile assets locally to have it compiled locally on development by command rake assets:precompile - but remember to delete it after tests to see changes in assets next time (it can be generated in vendor folder)

Answer 3

I am sure but you can try:

In application.js file write all js file in tree order like this:

//= require jquery

//= require jquery_ui

//= require jquery.ui.core