It’s a nosetests plugin that prints nicer dots grouped by class/module.
Install
From PyPI:
pip install nosenicedots
or from source:
pip install -e git+git://github.com/kumar303/nose-nicedots.git#egg=nosenicedots
Usage
nosetests --with-nicedots
Example
$ nosetests --with-nicedots
apps/devhub/tests/test_views.py:TestActivity
..............
apps/devhub/tests/test_views.py:TestAddVersion
.
======================================================================
FAIL: apps/devhub/tests/test_views.py:TestAddVersion.test_unique_version_num
----------------------------------------------------------------------
Traceback (most recent call last):
File "/path/to/apps/devhub/tests/test_views.py", line 3132, in test_unique_version_num
assert 0
AssertionError
apps/devhub/tests/test_views.py:TestCreateFoobar
..
apps/devhub/tests/test_views.py:TestDashboard
.....
apps/devhub/tests/test_views.py:TestDelete
..
======================================================================
FAIL: apps/devhub/tests/test_views.py:TestAddVersion.test_unique_version_num
----------------------------------------------------------------------
Traceback (most recent call last):
File "/path/to/apps/devhub/tests/test_views.py", line 3132, in test_unique_version_num
assert 0
AssertionError
----------------------------------------------------------------------
Ran 44 tests in 1.62s
FAILED (failures=1)
This new style of output is intended as a more useful test report and is inspired by py.test. Instead of a confusing (yet pretty) mess of dots you’ll see a printout of the module or class followed by dots that indicate each test in that group.
You’ll see the traceback for a failure immediately, which was designed for long running test suites. Note that the tracebacks are repeated again down at the bottom in case the output had scrolled off the screen already. Using --stop will not duplicate failure output.
It’s Also A Test Address
Each module or class group also doubles as an argument you can give to Nose if you want to re-run that group of tests. From the above output you could copy/paste and re-run tests in the TestActivity class like this:
$ nosetests --with-nicedots apps/devhub/tests/test_views.py:TestActivity apps/devhub/tests/test_views.py:TestActivity .............. ---------------------------------------------------------------------- Ran 14 tests in 0.62s OK
Caveats
If any other plugin needs to patch the unittest result then it will conflict with Nice Dots.
Python 2.5, 2.6 and 2.7 are supported at the moment. Other versions may or may not work. Python 3 is not yet supported. There are a few failing tests.
Metadata
Release files for nosenicedots 0.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| nosenicedots-0.5.tar.gz | 9.9 kB | Without provenance | Details for nosenicedots-0.5.tar.gz |
Release files / nosenicedots-0.5.tar.gz
| Download URL | nosenicedots-0.5.tar.gz |
|---|---|
| Size | 9.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
92ee3b86b5c1921c2d9dac217bef8990c5f852c8bc4d9018cafe0f3f3b81cd3a
|
|
BLAKE2b-256 checksum How to use checksums |
44c41d55fd44d68d6ecdf81a1a338231f9872b415a42fd6321b73b0056c351f8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for nosenicedots 0.5
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.