This is a fork of dlanger/nose-parallel. The behaviour of this fork will split tests amoung test files rather than individual tests. If you plan on using nose-parallel, I suggest you refer to the original fork.
A plugin to help split up your tests runs across multiple machines.
In an ideal world, test suites should be fast enough that they can be run locally on a single machine without extra engineering. This plugin is there to help when you can't make that to happen.
This won't help you run tests in parallel on one machine in different threads; that's what the built-in multiprocess plugin is for.
This will help you split up your test suites so that you can run the suites on multiple machines and not have the same test run twice - think Jenkins with the multijob plugin, or CI services like CircleCI.
Please refer to dlanger/nose-parallel.
On each machine:
- Export environment variables
NODE_TOTAL(the number of machines on which the suite will be run) and andNODE_INDEX(the 0-based index of the current machine) - Run nosetests with the
--with-parallelflag - Do something to join the results from all the machines back together
For example, this is how we'd run nosetests on the second machine in a four-machine testing cluster:
NODE_TOTAL=4 NODE_INDEX=1 nosetests --with-parallelIf you don't set those variables, nose-parallel will do the right thing and run all your tests.
The CircleCI versions of the environment variables (CIRCLE_NODE_TOTAL and CIRCLE_NODE_INDEX,
respectively) are also natively supported.
If you want to further randomize the distribution of tests, so
that the same test cases don't always run together on the same node, you may
use the --parallel-salt option to specify a salt value (e.g. a build
number, the day of the month). The salt must be the same on each node
during a parallel build, otherwise some test cases might be missed.
Alternatively you can set environment variable NOSE_PARALLEL_SALT. And, as
an added convenience, you can change this environment variable to something
your build environment already configures for each build with the option
--parallel-salt-env. E.g. on CircleCI you could do:
nosetests --with-parallel --parallel-salt-env CIRCLE_BUILD_NUMnose-parallel is released under the MIT license.
- Check for open issues or open a fresh issue to start a discussion around a feature idea or a bug.
- Fork the repository on GitHub to start making your changes to the master branch (or branch off of it).
- Send a pull request and bug the maintainer until it gets merged and published.
- Add yourself to the authors list in
setup.py
- @mahmoudimus, whose nose-timer plugin this is based off of