pytest-watch a zero-config CLI tool that runs pytest, and reruns it when a file in your project changes. It beeps on failures and can run arbitrary commands on each passing and failing test run.

Whether or not you use the test-driven development method, running tests continuously is far more productive than waiting until you're finished programming to test your code. Additionally, manually running py.test each time you want to see if any tests were broken has more wait-time and cognitive overhead than merely listening for a notification. This could be a crucial difference when debugging a complex problem or on a tight deadline.

$ pip install pytest-watch

$ cd myproject
$ ptw
 * Watching /path/to/myproject

Note: It can also be run using its full name py.test.watch.

Now develop normally and check the terminal every now and then to see if any tests are broken. Alternatively, pytest-watch can notify you when tests pass or fail:

• OSX

  $ ptw --onpass "say passed" --onpass "say failed" --nowatchdirs ".dont_look_here"

  $ ptw --onpass "growlnotify -m \"All tests passed!\"" \
        --onfail "growlnotify -m \"Tests failed\""
        --nowatchdirs ".dont_look_here"

  using GrowlNotify

• Windows

  > ptw --onfail flash using Console Flash

• xdist offers the --looponfail (-f) option (and distributed testing options). This instead re-runs only those tests which have failed until you make them pass. This can be a speed advantage when trying to get all tests passing, but leaves out the discovery of new failures until then. It also drops the colors outputted by py.test, whereas pytest-watch doesn't.
• Nosey is the original codebase this was forked from. Nosey runs nose instead of pytest.

1. Check the open issues or open a new issue to start a discussion around your feature idea or the bug you found
2. Fork the repository
3. Send a pull request

Use this software often? Please consider supporting me on