Helper utility to run multiple nosetests suites. Mostly used for making makefile scripts.
This utility runs multiple nosetest suites and merges their xml reports using xunitmerge. The advantage of this utility is that it guarantees that all nosetests suites are executed even if any of them fails (exit status >0). This is especially useful if multiple nosetests need to be run in Makefile script because normally, if any of them will fail, the rest of the script wont get executed which will skew the nosetests xml report as well as coverage data which are especially useful for CI systems such as Jenkins.
You can install multinosetests using pip:
$ pip install multinosetests
You can use the utility via an executable multinosetests:
$ multinosetests --help $ multinosetests "nosetests tests/foo -sv --with-xunit --with-coverage" \ "nosetests tests/bar -sv --with-xunit --with-coverage"
To run the tests you need to install testing requirements first:
$ pip install -r requirements-dev.txt
Then to run tests, you can use nosetests:
$ nosetests -sv
None yet. Why not be the first?
The MIT License (MIT)
Copyright (c) 2014 Dealertrack Technologies
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
TODO: Figure out how to actually get changelog content.
Changelog content for this version goes here.