Hey all... I just published a rudimentary package for exporting node.js
code coverage data to http://coveralls.io/ which lets you add a nifty code
coverage button to your package's README, as seen here:
https://github.com/cainus/urlgrey#readme and gives you nice reporting like
https://coverall
Oh! I didn't know about coveralls.io
It's looks good.
I will apply your package to my project.
Thank Gregg
On Sun, Mar 24, 2013 at 11:50 AM, Gregg Caines wrote:
> Hey all... I just published a rudimentary package for exporting node.js
> code coverage data to http://coveralls.io/ which lets you
Will this with work with the reports generated by Istanbul?
https://github.com/gotwarlost/istanbul
-- Daniel R. [http://danielr.neophi.com/]
On Sat, Mar 23, 2013 at 10:50 PM, Gregg Caines wrote:
> Hey all... I just published a rudimentary package for exporting node.js
> code coverage data t
If you send me example json output from istanbul, I can make it work pretty
easily... I couldn't figure out what istanbul was outputting from its
README other than html.
On Sun, Mar 24, 2013 at 10:56 AM, Daniel Rinehart wrote:
> Will this with work with the reports generated by Istanbul?
>
> htt
Actually... Istanbul looks like it can generate an lcov .info file. That
should be fine. I'll give it a go.
G
On Sun, Mar 24, 2013 at 10:56 AM, Daniel Rinehart wrote:
> Will this with work with the reports generated by Istanbul?
>
> https://github.com/gotwarlost/istanbul
>
>
> -- Daniel R. [
I'm pretty sure that istanbul's lcov output should work now, in the latest
version of coveralls. Can you let me know if you try it and see any
problems?
Thanks!
G
On Sun, Mar 24, 2013 at 10:56 AM, Daniel Rinehart wrote:
> Will this with work with the reports generated by Istanbul?
>
> https:/
