fxa-auth-server: code coverage

Sergi Mansilla sergi at comoyo.com
Wed Nov 20 01:27:50 PST 2013


Nice! I wrote a post some time ago about test coverage using Istanbul, and I use it successfully in some of my projects in GitHub, just in case you are still deciding.

http://sergimansilla.com/blog/test-coverage-node/

Cheers,

Sergi Mansilla

On 20 Nov 2013 at 02:36:59, Edwin Wong (edwong at mozilla.com) wrote:

hacked a bit on code coverage today. I tried istanbul, tap’s code coverage, and node-coverage which is what persona used.  

## Using node-cover:  
the easiest to run!  
http://people.mozilla.org/~ewong2/cover_html/  
Notes: https://github.com/mozilla/persona/pull/2272  

## Using Istanbul:  
http://people.mozilla.org/~ewong2/istanbul_cov/lcov-report/  
*Low confidence* in the numbers here, not sure if it’s merging runs correctly.  

## Using TAP’s experimental code coverage: I got parse errors:  
Edwin at edog:~/github/mozilla/fxa-auth-server$ TAP_COV=1 tap ./test/run/verification_tests.js --cover=./lib --coverage-dir=./coverage  
path.existsSync is now called `fs.existsSync`.  

/opt/local/lib/node_modules/tap/node_modules/runforcover/node_modules/bunker/node_modules/burrito/index.js:26  
throw e;  
^  
SyntaxError: Unexpected token: punc ({)  
at line 0:444 in expression:  


cheers,  
Edwin  
_______________________________________________  
Dev-fxacct mailing list  
Dev-fxacct at mozilla.org  
https://mail.mozilla.org/listinfo/dev-fxacct  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/dev-fxacct/attachments/20131120/6941549f/attachment.html>


More information about the Dev-fxacct mailing list