Tests

[rvagg]

A test script, currently deployed:

$ curl -sL https://deb.nodesource.com/test | sudo bash -

Tests npm install, npm start, npm test, native add-on build, simple http server, http client, buffers

Cleans up after itself, the only thing left intact would be source files in ~/.node-gyp/.

[rvagg]

@othiym23 is there anything you think worth adding in here to test the success and usability of an npm installation? Mainly targetting Linux but should work on Mac too. We'll be using this script as we adjust and expand our binary distribution targets.

[othiym23]

Sorry, just got to this. Here's the best way to smoke test npm:

1. clone npm
2. make install, which will install the devDependencies and build the docs
3. npm run-script test-all, which will run both the legacy tests (which pretty heavily exercise npm all on their own) and the tap tests
4. npm -g install yo generator-angular && mkdir angular-test-app && cd angular-test-app
5. yo angular, filling out the prompts

If it can install and build an entire Angular-scaffolded app, it's probably good to go.

Some of these tests may best be considered optional. 1-3 get run before every release of npm, though, and I'll probably mix 4-5 into the rotation just because they hammer the codebase so hard.

[rvagg]

nice, I might build an advanced-mode test with this in it for when we're really unsure, like with CentOS 5 / RHEL 5

[dshaw]

Thanks, @othiym23