apocas
badge support!
maybe we could integrate this with https://github.com/rvagg/nodei.co ?
so that you can generate a nodei.co badge that has the test status on it
cc @rvagg
if we could get an API endpoint for nodechecker.com then I could easily add that to the badge ... but, aren't travis/drone/etc. badges good enough for test status for those that would care? people that don't have tests are unlikely to want to opt for "test staus" on their badge.
Part of why I like node checker is that it does it whether you want it to or not. So I was thinking of e.g a chrome plugin that showed the nodei.copng in github readmes that don't already have it
On Friday, January 3, 2014, Rod Vagg wrote:
if we could get an API endpoint for nodechecker.com then I could easily add that to the badge ... but, aren't travis/drone/etc. badges good enough for test status for those that would care? people that don't have tests are unlikely to want to opt for "test staus" on their badge.
— Reply to this email directly or view it on GitHubhttps://github.com/apocas/nodechecker.com/issues/3#issuecomment-31572983 .
ah! now that would be interesting, being able to automatically see things like download counts, number of npm stars etc on github pages would be neat, and yeah, test status too would be handy.
just brainstorming here, but a project like nodechecker combined with nodei.co and testling-ci would be soooo amazing, especially when combined with https://github.com/rvagg/nodei.co-chrome
e.g. if I open a github repo of a node module, but the author has a really barebones readme (no badges etc), I should be able to see:
- if the module is on npm
- if the module has a passing test suite on the latest version of node
- if the module works with browserify
- which browsers the browserified test suite passes in
I imagine browserify doesn't work so well with a lot of test frameworks out there and this could be a problem. Unless you just restrict it to certain test runners but then you'd miss out on a whole lot of packages.
Damn that chrome plugin idea is awesome!!!!
Yeah browserify may be tricky like @rvagg said, due to all the stuff that is out there.
I'm currently refactoring nodechecker to a more agile architecture removing unnecessary complexity. Will launch it this weekend and then I will start looking into this :)
I agree that testing every module in a browser would be hard, so maybe it makes sense to start with the easy case which I guess is to take the npm test command and try to browserify it?