test: Fix PHPUnit 11 use in Behat #56922
Merged
Conversation
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
danxuliu
requested review from
leftybournes,
salmart-dev and
yemkareems
and removed request for
a team
Starting with PHPUnit 11.3, some complex outputs of certain asserts (like "assertStringContainsString") require the output of PHPUnit to be explicitly setup. Otherwise when the assert fails a type error is thrown (although it does not seem to affect asserts with simpler outputs, like "assertEquals"). Signed-off-by: Daniel Calviño Sánchez <[email protected]>
danxuliu
force-pushed
the
fix-phpunit-11-use-in-behat
branch
from
ba22d25 to
19c9d88
Compare
CarlSchwan
approved these changes
Dec 13, 2025
nickvergessen
approved these changes
Dec 15, 2025
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.
Follow up to #55870
Starting with PHPUnit 11.3, some complex outputs of certain asserts (like
assertStringContainsString) require the output of PHPUnit to be explicitly setup. Otherwise when the assert fails a type error is thrown (although it does not seem to affect asserts with simpler outputs, likeassertEquals).Note that PHPUnit asserts have never been intended to be used as standalone methods, even if it worked and it was recommended by Behat. In the future it might be needed to move to a different library, but for now this adjustment seems to be enough.
How to test
Result with this pull request
The output shows the actual and expected texts
Result without this pull request
A type error is thrown:
Type error: PHPUnit\TextUI\Configuration\Registry::get(): Return value must be of type PHPUnit\TextUI\Configuration\Configuration, null returned (Behat\Testwork\Call\Exception\FatalThrowableError)