@rmg @piscisaureus

Just realized this is a problem. I need to do some setup in ./test/ before running the tests. I believe my options are:

- preinstall/post-install: works great during dev, because install is used to setup local dev dependencies, but it also means that anybody who does an `npm install -g strong-supervisor` gets this setup... sucky

- pretest: runs before every npm test, making it brutally slow

- something specific to SL's CI

The install script really needs to know about the purpose for which install is being called. Is it a local install, in the repo, that will bring in all the test dependencies? Is it a dependency install, where the module will become a requireable dependency of another module? Is it a global install, where the modules bin: scripts will be installed into the PATH?

These things are different, npm calling them all "install" is pretty bad, especially when it knows they are different (it does different things for these cases).

I favor making it good for strongloop toolbox users doing an `npm install -g` over making it good for developers: so I might remove the pre-install, and add a note to the README saying "thout must run test-install.sh" before doing an `npm test`. But for ci... what do you think? Add a pre-test-setup script, only understood by sl-ci-run?