Support external tox.pytest usage via "test" extra #3422
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In order to allow plugin writers to easily pull in all dependencies needed to use the `tox.pytest` module, add a new `test` extra with a subset of the test dependency group. Though the pytest package should be present in the users' environment anyway, we still add it for consistency and to produce a conflict just in case the version has been constrained to an older version by the project.
gaborbernat
approved these changes
Oct 22, 2024
CyclingNinja
added a commit
to CyclingNinja/package-template
that referenced
this pull request
Oct 28, 2024
In line with tox-dev/tox#3422
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In order to allow plugin writers to easily pull in all dependencies needed to use the
tox.pytestmodule, add a newtestextra with a subset of the test dependency group. Though the pytest package should be present in the users' environment anyway, we still add it for consistency and to produce a conflict just in case the version has been constrained to an older version by the project.Fixes #3415
tox -e fix)docs/changelogfolderNot sure how to test this without splitting off the plugin tests into an extra test-suite, which seems like quite the invasive change.
Also did not find a good place to update this in the docs without starting a whole new section on testing plugins with pytest.