Open toolness opened 9 years ago
:+1: on test coverage being added to the standard for automated testing. Have you played with coveralls?
Sidenote: This feels like a weird place for this issue... move to handbook?
Rad! I haven't played w/ coveralls but it looks like a great solution. I've only used jscover or jscoverage or something that required a C compiler and doing weird stuff with index.js files, so something easier would be quite welcome!
Sidenote: This feels like a weird place for this issue... move to handbook?
Oh, Simon actually wanted me to file it here, but I may have misinterpreted him.
Whoops! Ok... sorry about that. Retracted
In MozillaFoundation/MoFo-Engineering-Handbook#30 we are discussing automated testing best practices, and thought it would be rad to show test coverage for every repository that supports it (possibly defaulting to 0% coverage if there's no support). What do you think? And what would the protocol be for reporting test coverage? Would Travis CI ping a metrics server every time the master branch was tested or something?