Grunt has a task to watch current folder. I just stumbled across these
commands by luck but they seem to create a nice simple flow to get
started testing and writing code.
cd ~/Grunts
git init
grunt init:commonjs
(enter .git for git repo path)
Now you have a grunt managed project!
I then ran:
grunt watch
and opened a new terminal pane using iTerm2 in the same window ⌘D
then, opened vim and changed lib/Grunts.js to return axxxsome instead
of 'awesome'. Voila the other pane that is `watching` spits out a nice
list of trace statements. It runs /nodeunit/ tests but still, if i'm
starting out, I think this is easier than getting a similar workflow
working without ruby.
Dave
On Fri, Jun 15, 2012 at 8:26 PM, bernardo <
bfa...@gmail.com> wrote:
> Ciao Nicola,
>
> Sei italiano immagino?
>
> Found your post looking for ways to get js coverage through jasmine myself.
> To answer your questions:
> 1) Jasmine by itself, even with Jasmine-jquery, works great with JTSD, I've
> experimented myself and it definitely works.
> 2) If you need a browser environment to load html fixtures (you technically
> don't, you can use things like env.js) JTSD is even more so the right
> choice, as it actually does run tests in 'registered' browsers so you get a
> full browser environment.
>
> I wasn't able to get JTSD to work for my specific application because I also
> use requireJS for AMD loading and it seems to be highly incompatible with
> JTSD.
> So the question remains - what other tool could I/we use to collect code
> coverage in a jasmine environment?
>
> Thanks!
> --
> You received this message because you are subscribed to the Google Groups
> "Jasmine" group.
> To view this discussion on the web visit
>
https://groups.google.com/d/msg/jasmine-js/-/Wi1VPADmgi0J.
>
> To post to this group, send email to
jasmi...@googlegroups.com.
> To unsubscribe from this group, send email to
>
jasmine-js+...@googlegroups.com.
> For more options, visit this group at
>
http://groups.google.com/group/jasmine-js?hl=en.