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:
tests/src/foo/bar/* tests/src/foo/biz/*
(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.)
Config
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:
--quickunit-prefix=tests/unit/ --quickunit-prefix=tests/integration/
Or, if you’d prefer, via setup.cfg:
quickunit-prefix = tests/unit
tests/integration
Or, via setup.cfg:
quickunit-json = -
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
File details
Details for the file nose-quickunit-0.5.4.tar.gz.
File metadata
- Download URL: nose-quickunit-0.5.4.tar.gz
- Upload date:
- Size: 5.2 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
6134ac087a032f043899bbf2d46f755d1754491d1abda74dafbb0144c7267b86
|
|
| MD5 |
f1772c3d932e0c0d0ec204cd8480efbe
|
|
| BLAKE2b-256 |
515eb84b16ee282ac2f9df39c357feae035dd3f73d8c9cf24a77fd856d5e3377
|