Given standard test setup, will determine which tests need to run against a given diff.
For example, say you're working in your branch called my-new-sexy-feature, which modifies the following files:
src/foo/bar/__init__.py src/foo/bar/baz.py src/foo/biz.py
Now if we run with the default options, nosetests --with-quickunit, it will look for tests (by default) in the following base directories:
(It does this by analyzing the diff against git merge-base HEAD master, and determining which files you've changed are tests, including them, and which files containing test coverage in a parallel directory.)
It will also report coverage based on the tests run, and optionally dump that to a JSON file.
If you want to support multiple directories for searching (let's say you break up unittests from integration tests) you can do that as well:
Or, if you'd prefer, via setup.cfg:
quickunit-prefix = tests/unit tests/integration
To output the coverage report as a JSON file, you can use simply use the quickunit-output option:
Or, via setup.cfg:
quickunit-json = -