Live data from Hacker News

Istanbul: A JavaScript code coverage tool written in JS

gotwarlost.github.io

11–18 of 18 posts

Re: Istanbul: A JavaScript code coverage tool written in JS

#12
Great tool, perfectly fits to the node.js ecosystem, lightweight and fast.

However in case you use co-mocha[1] to test your generators, istanbul won't work properly, the generators in the reports are shown as uncovered. Therefore I made a mocha fork[2] and directly applied the changes from co-mocha to the source (instead of monkey patching); it solved the problem.

[1] https://github.com/blakeembrey/co-mocha [2] https://github.com/tfitos/mocha

Re: Istanbul: A JavaScript code coverage tool written in JS

#14
i have some projects where the meat is in a cross domain connector. no way to test it in units. only functional test in real browsers cut it. otherwise it's just red tape testing.

there is zero coverage tool for this case, until browsers wake up and give me a decent Dev api like opera 12 allowed

Re: Istanbul: A JavaScript code coverage tool written in JS

#15

In case it's useful for anyone, here is a gist of a gulpfile I use to use Istanbul to instrument my Node.js app, then run tests with Mocha and output the results: https://gist.github.com/medatech/76c6017cf55630b2db08

or you could just write it as a single CLI command: https://github.com/strongloop/express/blob/master/package.js...

Re: Istanbul: A JavaScript code coverage tool written in JS

#16
post #8

Why did you name it Istanbul?

> Why the funky name? > Since all the good ones are taken. Comes from the loose association of ideas across coverage, carpet-area coverage, the country that makes good carpets and so on... https://github.com/gotwarlost/istanbul#why-the-funky-name

It made me think of the Neil Simon song.
Post reply on HN