-
Notifications
You must be signed in to change notification settings - Fork 2k
Make the PR-finalize symlink tests self-sufficient and drop a localized assertion #37039
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.
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
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
9ee6132
Make the symlink tests self-sufficient and drop a localized assertion
3430704
Merge commit 'ad8249ecbc90956bab7f972d293390b900c4423f' into PureWeen…
Copilot f845978
Prove the symlink candidates reach New-Item
Copilot 91bc8d1
Scope the New-Item wildcard comment to this invocation
Copilot File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
New-Itemwas attempted against$planted. I reproduced a mutant that generatesforced0, continues beforeNew-Item, then createsforced1: both symlink tests pass, and only the separate non-collision test fails (39/40). The tests therefore still rely on another backstop. Use a call-throughMock New-Item/spy to record attempted-Pathvalues and assert the first is$planted(anddangle0), or narrow the self-sufficiency claim.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed in f845978. You were right: generator consumption did not prove
New-Itemsaw the planted path. Both symlink tests now install a call-through PesterMock New-Itemthat records attempted paths while invoking the real cmdlet, then assert the planted link was attempt 1 and the next candidate was attempt 2. I replayed your exact skip-first mutant (forced0;continuebeforeNew-Item; createforced1): both symlink tests now fail directly (the real suite remains 40/40; all related suites 102/102).