Repository navigation
Preserve existing PHPUnit configuration files - #2044
Merged
MrPunyapal merged 3 commits intoNov 19, 2026
Merged
Conversation
Member
|
Thanks! |
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.
What:
Description:
Pest can remove an existing
.pest.xmlafter running with an explicit or discovered PHPUnit configuration. Two Pest runs in the same directory can also interfere when they both need a generated configuration.Create the generated configuration exclusively and clean it up when the process that created it exits. Keep the regular configuration path for a run without contention so Test Impact Analysis can still reuse its fingerprint.
The regression tests cover existing project files, generated files, parallel workers, and a generated path that is replaced during the run.
composer testpassed. Two concurrent CLI runs in the same fixture directory also held and removed their own configuration files. The ordinary and fallback paths both retained Test Impact Analysis replay on repeat runs. The shared success snapshot passed after regeneration with #2041, #2042, and #2043 applied together.