diff --git a/README.md b/README.md index ddf43f6..20b34cf 100644 --- a/README.md +++ b/README.md @@ -14,7 +14,7 @@ Motivation 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 +programming to test your code. Additionally, manually running `pytest` 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. @@ -69,19 +69,19 @@ $ ptw --beforerun init_db.py ``` Or after they finish, e.g. deleting a sqlite file. Note that this script receives -the exit code of `py.test` as an argument. +the exit code of `pytest` as an argument. ```bash $ ptw --afterrun cleanup_db.py ``` -You can also use a custom runner script for full `py.test` control: +You can also use a custom runner script for full `pytest` control: ```bash $ ptw --runner "python custom_pytest_runner.py" ``` -Here's an minimal runner script that runs `py.test` and prints its exit code: +Here's an minimal runner script that runs `pytest` and prints its exit code: ```py # custom_pytest_runner.py @@ -89,7 +89,7 @@ Here's an minimal runner script that runs `py.test` and prints its exit code: import sys import pytest -print('py.test exited with code:', pytest.main(sys.argv[1:])) +print('pytest exited with code:', pytest.main(sys.argv[1:])) ``` Need to exclude directories from being observed or collected for tests? @@ -118,11 +118,11 @@ Options: Otherwise, tests are interrupted on filesystem events. --beforerun Run arbitrary command before tests are run. --afterrun Run arbitrary command on completion or interruption. - The exit code of "py.test" is passed as an argument. + The exit code of "pytest" is passed as an argument. --onpass Run arbitrary command on pass. --onfail Run arbitrary command on failure. --onexit Run arbitrary command when exiting pytest-watch. - --runner Run a custom command instead of "py.test". + --runner Run a custom command instead of "pytest". --pdb Start the interactive Python debugger on errors. This also enables --wait to prevent pdb interruption. --spool Re-run after a delay (in milliseconds), allowing for @@ -161,7 +161,7 @@ Alternatives 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. + drops the colors outputted by pytest, whereas pytest-watch doesn't. - [Nosey][] is the original codebase this was forked from. Nosey runs [nose][] instead of pytest.