Skip to content
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

Jump to bottom

Update README.rst with pytest-xdist 3.0.2 news #174

Merged
merged 1 commit into from
Jun 19, 2024
Merged

Update README.rst with pytest-xdist 3.0.2 news #174

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 2 additions & 2 deletions README.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -137,10 +137,10 @@ The downsides of this method are that there is a relatively large
overhead for running each test and that test runs are not completed.
This means that other pytest features, like e.g. JUnit XML output or
fixture teardown, will not function normally. The second issue might
be alleviated by using the ``--boxed`` option of the pytest-xdist_
be alleviated by using the ``--forked`` option of the pytest-forked_
plugin.

.. _pytest-xdist: https://pypi.org/project/pytest-xdist/
.. _pytest-forked: https://pypi.org/project/pytest-forked/

The benefit of this method is that it will always work. Furthermore
it will still provide you debugging information by printing the stacks
Expand Down
Loading