NOTE: Credit for the idea goes to Jeff Wrinkler. Today there are other versions of this on PyPI (one called nosy and another called nosyd) but I didn't like the config file required in both cases.
What makes this version different, and better IMHO, is that Nosy simply acts as a passthrough to the underlying commandline test runner. You don't have to learn how to use a new test tool and create a config file you just replace the normal commandline with nosy and get on with your life.
So if you normally run nosetests like this::
$ nosetests --nocapture --with-coverage --cover-package= mypackage
You can simply run nosy instead of nosetests like this to have your tests rerun whenever the code changes::
$ nosy --nocapture --with-coverage --cover-package= mypackage
Nosy currenly walks the working directory for *.py files and only re-runs when *.py files change.
- integrate building documentation
- run syntax checker (pyflakes / pylint)
- rename and publish on pypi? """