node.js ko
npmpants – We test npm modules for you
npmpants – We test npm modules for you
by hollaback
npmpants is a testing service for all npm modules. You save time you would have spent agonizing over broken code!
See test results for the most popular modules, and steer clear of broken modules :) Over 500 modules tested!
Nest shows a module’s compatibility with multiple node versions and operating systems (e.g. Solaris, Linux, Mac).
Judging Instructions
Go to http://npmpants.org/ and type in the name of the module you’re like to see. Test results for that module are then displayed.
The homepage also shows realtime updates of recently tested and published modules, and the billboard shows a gigantic list of the test results for the node modules we’ve tested.
Note: certain modules will not have test results. This may be because their package.json does not have a scripts.test command. Also, certain test commands do not return the correct exit code, and are labeled failed (future versions of the app will include a yellow warning designation for this case).
We recommend checking out dht-bencode and express.
express results screenshot:
dht-bencode results screenshot:
Who
DTrejo — Providence, Rhode Island
ericz — Berkeley
morganrallen — Oakland, CA
steveWang — Berkeley, CA
How
The master webserver serves the website and listens to npm in order to send “please test this” updates to slaves. The master server also listens for recent test results, and notifies the homepage to display these new results.
The test-runner slaves use a handler depending on the test framework used. We wrote handlers for vows, expresso, tap, nodeunit, node-jasmine, and whiskey. We also wrote a generic handler for things like make and cake, which return exit codes based on their success or failure.
We have run slaves on running on Solaris, Linux, and Mac OS X.
The following tools allow the service to function: http://search.npmjs.org, couchDB (cradle, request), nowjs.com, express, nko, and many testing frameworks (vows, tap, expresso, nodeunit, jasmine, and whiskey).
Votes
Your Vote
Voting is now closed.
Other Votes
(17)
b00giZmjudge
robhawkesjudgeCool idea, although some of my favourite modules like Socket.IO had absolutely no results so it isn’t amazingly useful to me at the moment. Also, the billboard wasn’t loading for me so I couldn’t go through the list of existing modules. Still, I’m a fan of anything that helps makes working with Node packages an easier experience.
adinardijudgeVery useful and would be great to start exposing even more info (which tests are failing, perhaps even last x lines of run output, etc). I wonder if adding a metod of notifying authors of breakages would be useful (probably more accepted if part of NPM and not a third-party service — a required part of being part of npm).
trycatcherjudgeI like it! The auto-completion is a nice touch. Would be cool to see this get integrated into npmjs.org
allancajudgeSlick. Could be really helpful. Like the idea. As it stands, not really useful since everything is marked failing.
3rd-Eden
contestantI’ll try to judge fairly because I know many of you guys from the nowjs fame.
The project reminds kinda reminds me of
testswarmbut for npm packages instead.One of the biggest misses is the lack of navigation on the site, there is no menu, no breadcrumbs what so ever, while we can navigate pages using the next and back buttons..
The UI is rather simple, but it serves it’s purpose, displaying the information. But some nicely styled elements would have just made it a bit more visually appealing.
The billboard can use some filtering, sorting in order for it to be useful it’s just one big ass dump data now.
When searching for packages, for example
nowit doesn’t yield any test results, probably because they are not specified in the package.json but it would be nice if you be notified of that instead of ano resultsmessage, it kinds makes it feel like the application is failing.But overal, this is one great application and would love to see it be refined after the competition because it has some really great potential. So GJ on that.
janljudgeNice job, we should roll this into npm proper.
dapsaysjudgeGreat idea! It’s surprising how many modules' tests are failing on all platforms and versions.
- contestant
The reason for this is that with a large number of packages their test frameworks are actually failing or return a non-zero error code. We didn’t get to the part where we could determine which was the case but if your test suites fails obviously none of your tests are passing. Thanks for the review.
jsjohnstjudgeLove the concept and definitely will leverage this! Hoping you OS this as it’s something I would contribute too. Couple suggestions:
1) Show which tests fail 2) Ability to specify the version to test 3) Ability to test a github repos URL as well as a published npm
Great work!
cistov
contestant
therazorbladejudgeExpress completely broken? This can’t be right. How exactly do you test? Also, the live stream showing tested modules but when searching for them showing no results.
- contestant
It appears the reason for this is that the tests themselves fail. Running
make testmanually fails will an error. Unfortunately we didn’t get to the point in the project to make this clear. In the end we want to implement a green/yellow/red type system where yellow would be a test suite failure, not necessarily actual failed tests. - therazorbladejudge
Makes sense. Thanks for clarifying.
hij1nxjudgeAlthough neat, the billboard is simply noise from a usability perspective, some clever analytics would have been very cool. overall i really like this though. nice work you guys.
- contestant
Yup, I agree. It was really down to the last minute getting that working as it is. Future work will really clean that up. Thanks for the review! (Oh how I wish i’d had the time to get Weld in!)
aaronheckmannjudgeVery very useful.
mikealjudgei don’t see any instructions on what a module needs to define for you to be able to run it’s tests.
- contestant
The last paragraph in the Judging Instructions says it.
Note: certain modules will not have test results. This may be because their package.json does not have a scripts.test command. Also, certain test commands do not return the correct exit code, and are labeled failed (future versions of the app will include a yellow warning designation for this case).
Coreh
contestantThis is really, really useful. Here are a couple of suggestions:
Work a bit more on the design side of the page.
Make a command line version, that one could use locally (something like
$ nest package-name, and then it would print results similar to the ones provided by the site).Add the option of users voting and rating on packages.
- contestant
Thanks! These are some of the things we are working on. There is currently a really dumb CLI available. Next steps we are taking are integrating GitHub login so package owners can claim ownership and get alerts. Everyone else will be able to watch modules. The end goal is to alert people of a dependency breaks an important module.
ncb000gt
contestantUseful too, however, it says that my tests all failed, both for bcrypt and cron. This is unlikely but possible however I have no way to see what about them failed. As such I see that as more to do. However, it’s certainly useful to have the tests run for people so that they know whats up.
shiawuen
contestantWould be great if I can search multiple modules at the same time
- contestant
What would you be looking for in this? Something like the billboard view with a selection of your chosen packages?
shiawuen
contestantSay I wanted to use a few modules for my project then I can type them all in the textbox and separate with comma. Basically to provide an overview of the modules that I choose is safe to use or not.
e.g, express, mongoose, dnode
henrikberggrenjudgeGreat utility. Although no scores turned up when I tried.
- contestant
Hey Henrik, not sure which page you were on, but this may have been an issue with socket.io/http-proxy/newest websockets on the no.de platform.
We just updated socket.io, so hopefully this helps things along.
Cheers and thanks!
- henrikberggrenjudge
Hey, still not working for me. ex. http://hollaback.no.de/modules/#mailchimp
- contestant
Did you click that from ‘Recently updated on npm:’ We didn’t get to the filtering part on that and everything from npm is added, weather is has tests or not. And in the case of mailchimp, there are no tests available. The section below that ‘Recently tested:’ should have better results.
- henrikberggrenjudge
Yes, clicked from recent. But also tried redis-node for example.
- contestant
Odd, I’m not sure how you’re getting this as redis-node doesn’t define scripts.test in package.json
- henrikberggrenjudge
Checked out more now and found one that works, nice job. Maybe filter out the ones that doesn’t have any tests… Makes browsing a bit easier :)
- contestant
Nice! Thanks Henrik. Yeah, that is where we fell short on time.
MEgrez
contestantMaybe in the future this help me to configure node machine in the right way!
- contestant
Did you click that from ‘Recently updated on npm:’ We didn’t get to the filtering part on that and everything from npm is added, weather is has tests or not. And in the case of mailchimp, there are no tests available. The section below that ‘Recently tested:’ should have better results.
- contestant
Sorry, replied to the wrong comment.
pcaprjudgeReal-time CI builds for npms! Giving 5 stars for design because the app looks great, given you only had 48 hours. Great use of nowjs for the real-time billboard.
paularmstrong
contestant
Like it a lot! This would make a great addon for npmjs.
For me it’s not entirely useful at this point of time (missing tests for some popular node modules, no detail views), but I think this could be pretty huge, if you guys stay on track with this project. Kudos! :)