Repository navigation
🧪 test: run template tests without symlink privileges - #283
Merged
gaborbernat merged 4 commits intoOct 27, 2026
Merged
Conversation
The PR changes only the test suite, so it has no user-facing release note; CONTRIBUTING.md asks for the `skip news` label instead of a fragment. Type the template path Final like the other locals in the test modules.
gaborbernat
changed the title
Pytest injects fixtures and parameters as arguments, so test signatures grow past the argument limits. Ignore the two rules for tests in the config and drop the inline suppressions.
This file contains hidden or 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
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.
Contributors on Windows without permission to create symbolic links, which
os.symlinkneeds there, could not run the suite: 65 environment-loading and verbose-output tests failed withWinError 1314before reaching the plugin. 🪟 With this change the suite runs on such accounts too.Each generated pytester project now gets a small entry module that executes the shared env-checking template from its original location, where a symlink used to point at it. Running the original file keeps coverage attributed to the template, which a plain copy would lose. The plugin is unchanged, so the PR carries no release note.