From 788194d749f4737d9608807aa081c0213043760f Mon Sep 17 00:00:00 2001 From: Jordan Pittier Date: Thu, 23 May 2019 15:58:45 +0200 Subject: [PATCH] Doc: advanced.rst: Use "pytest" as the new recommended entrypoint for Pytest According to https://github.com/pytest-dev/pytest/issues/1629 the recommended entrypoint for `pytest` is `pytest`. Usage of `py.test` has been deprecated for 2 years now. --- docs/advanced.rst | 6 +++--- news/3759.doc.rst | 1 + 2 files changed, 4 insertions(+), 3 deletions(-) create mode 100644 news/3759.doc.rst diff --git a/docs/advanced.rst b/docs/advanced.rst index 3ac323e6..90654436 100644 --- a/docs/advanced.rst +++ b/docs/advanced.rst @@ -467,7 +467,7 @@ and the corresponding Makefile:: pipenv install --dev test: - pipenv run py.test tests + pipenv run pytest tests Tox Automation Project @@ -483,7 +483,7 @@ and external testing:: deps = pipenv commands= pipenv install --dev - pipenv run py.test tests + pipenv run pytest tests [testenv:flake8-py3] basepython = python3.4 @@ -492,7 +492,7 @@ and external testing:: pipenv run flake8 --version pipenv run flake8 setup.py docs project test -Pipenv will automatically use the virtualenv provided by ``tox``. If ``pipenv install --dev`` installs e.g. ``pytest``, then installed command ``py.test`` will be present in given virtualenv and can be called directly by ``py.test tests`` instead of ``pipenv run py.test tests``. +Pipenv will automatically use the virtualenv provided by ``tox``. If ``pipenv install --dev`` installs e.g. ``pytest``, then installed command ``pytest`` will be present in given virtualenv and can be called directly by ``pytest tests`` instead of ``pipenv run pytest tests``. You might also want to add ``--ignore-pipfile`` to ``pipenv install``, as to not accidentally modify the lock-file on each test run. This causes Pipenv diff --git a/news/3759.doc.rst b/news/3759.doc.rst new file mode 100644 index 00000000..5aebd29e --- /dev/null +++ b/news/3759.doc.rst @@ -0,0 +1 @@ +Updated the documentation with the new ``pytest`` entrypoint.