Skip to content

Issue 11354 fixing docs for lfnf #11361

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
nicoddemus merged 9 commits into from
Aug 29, 2023
Merged

Issue 11354 fixing docs for lfnf #11361

Changes from 1 commit
Commits
Show all changes
9 commits
Select commit Hold shift + click to select a range
b98d293
docs: changing some docs for last-failed-no-failures
seanjedi Aug 26, 2023
66e7a1f
docs: improve --lfnf docs to make functionality more clear
seanjedi Aug 27, 2023
3be5d3e
Merge branch 'pytest-dev:main' into issue_11354-Fixing-docs-for-lfnf
seanjedi Aug 27, 2023
722b487
Merge branch 'pytest-dev:main' into issue_11354-Fixing-docs-for-lfnf
seanjedi Aug 28, 2023
75e815f
docs: updating the docs to make --lfnf more clear
seanjedi Aug 28, 2023
e431b8e
docs: Add a bit more to the doc for --lfnf
seanjedi Aug 28, 2023
e121c50
docs: quick change
seanjedi Aug 28, 2023
5ac0a7a
Update src/_pytest/cacheprovider.py
nicoddemus Aug 28, 2023
02f84bc
docs: Added the name of the option we are changing the docs for
seanjedi Aug 28, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
docs: quick change
  • Loading branch information
@seanjedi
seanjedi committed Aug 28, 2023
commit e121c50235bfab686df4ad60c0b150801832aee9
11 changes: 9 additions & 2 deletions doc/en/how-to/cache.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -180,10 +180,17 @@ This option governs the behavior of ``--last-failed``.
Determines whether to execute tests when there are no previously (known)
failures or when no cached ``lastfailed`` data was found.

There are two options:

* ``all``: when there are no known test failures, runs all tests (the full test suite). This is the default.
* ``none``: when there are no known test failures, just emits a message stating this and exit successfully.

Example:

.. code-block:: bash

pytest --last-failed --last-failed-no-failures all # when there are no known test failures, runs the full test suite again (default behavior)
pytest --last-failed --last-failed-no-failures none # when there are no known test failures, runs no tests, emits a message about no known failures and exits successfully
pytest --last-failed --last-failed-no-failures all # runs the full test suite (default behavior)
pytest --last-failed --last-failed-no-failures none # runs no tests and exits successfully

The new config.cache object
--------------------------------
Expand Down