add test script to package.json #70

Merged
merged 1 commit into from Sep 5, 2011

Projects

None yet

3 participants

@isaacs
Contributor
isaacs commented Sep 4, 2011

It's very hard to retrain my fingers to not type npm test to run all the tests. Plus, this is good for CI hooks and such.

Also: looks like the timeout test is failing on node 0.4.11.

@dscape
dscape commented Sep 5, 2011

@issacs what do you use to test on multiple nodes? That looks handy!

@isaacs
Contributor
isaacs commented Sep 5, 2011

@dscape I usually use https://github.com/isaacs/node-tap for new projects, and I've been trying to backport my existing stuff onto it. Sometimes I just hack up a bash or node script to output tap-formatted text to stdout.

@dscape
dscape commented Sep 5, 2011

@isaacs I've seen that - just didn't have time to port my tests to node-tap yet. Im very interested in replacing vows with node-tap in the little ensure script I wrote. I wrote it mostly cause I wanted to read test code in my tests, and it was before I learned about tap.

However I was asking how do you test multiple versions of node at the same time? This would be great for publishing in npm. I'm always wondering if I broke the code in node 0.5, or something like that.

@isaacs
Contributor
isaacs commented Sep 5, 2011

@dscape I use https://github.com/isaacs/nave for that. It doesn't let you fire off a test suite in every version, but it's pretty easy to switch between them.

@mikeal mikeal merged commit 604f1fb into request:master Sep 5, 2011
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment