Hey Daniel,
it's better if you let testacular to serve it - it takes advantage of
heavy caching and reloading only files that has actually changed.
And you don't wanna start rails server in order to do JS unit testing...
My advice is to separate the JS stuff generated by rails, into a
single file + have static version of it (mock) to enable quick unit
testing.
Then, all you have to do in order to unit test, is just executing
"testacular config.js" and start editing your files (it can capture
browser in the background and run tests whenever you change any file)
- that's what you want !
Anyway, you can serve urls as well, just add into the config:
'
http://localhost:3000/js/application.js'
Btw your msgs get moderated, I guess that's because you are not member
of this mailing list ?
You can join the group and select, no email - than, you should be fine
posting...
V.
On Tue, Jul 24, 2012 at 7:25 PM, <
dnei...@squareup.com> wrote:
> Hi
>
> Thanks. I started using grunt to setup watches and compiling from coffee
> script, I didn't know about the autoWatch option.
>
> The application.js file is part of a rails application and should be served
> by the rails server (it gets pumped through the asset pipeline etc) Is there
> anyway to include a URL rather than a relative file?
>
> Cheers
> Daniel
>
https://groups.google.com/d/msg/testacular/-/sVHNJ0GU5wUJ.