[CodeQuality] Verify assert method name exists on Assert class via reflection#720
Merged
Conversation
…ion, fall back to renamed method
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.
AssertTrueFalseToSpecificMethodRectormappedfile_exists/is_dirtoassertFileNotExists()/assertDirectoryNotExists(). These were renamed in newer PHPUnit versions — the produced call no longer exists on theAssertclass, breaking the test.Now the rule verifies the target method exists on
PHPUnit\Framework\Assertvia reflection, and falls back to the current name when the legacy one is gone.Before
on PHPUnit 12 became:
After
Renames covered:
assertFileNotExistsassertFileDoesNotExistassertDirectoryNotExistsassertDirectoryDoesNotExistWhen the legacy method still exists (older PHPUnit), it is kept as-is.