Handle reserved keywords in test file names - #1804
Open
lazerg wants to merge 1 commit into
Open
Conversation
lazerg
force-pushed
the
fix/issue-1803-reserved-keyword-test-name
branch
from
July 31, 2026 13:01
eea7489 to
d87afb8
Compare
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
1 participant
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:
A test file whose name resolves to a PHP reserved keyword, such as
list.test.php, made Pest generatefinal class listand abort the run with aParseError. The class name now falls back to the existingInvalidTestNameplaceholder when it is not a valid identifier, so these files run like any other. The printable name still comes from the file path, so the reported output is unchanged.Related:
Closes #1803