As discussed on IRC, it would be nice with a single command, e.g. buster-dev-tools/bin/buster-all-tests, which would run the test suites for all the Buster modules. This can be implemented using buster -c */buster.js, and ./run-tests for the modules that require lower-level bootstrapping. The command should make sure to sum up the exit codes from the different test suites and use the sum as its own exit code.
buster -c */buster.js
I think the right thing to do here is to make npm test work for every module, then just add a command in buster-dev-tools that runs npm test on all the projects.
Make npm test work (busterjs/buster#183)
npm test now works for every module and with buster-dev-tools test npm test for every module is run. But due to the fact, that some modules generate a lot of output during the test run, it is hard to find out the overall state.