test: Don't use PHPUnit assertions in Behat's own test suite - #1872
Open
carlos-granados wants to merge 2 commits into
Open
test: Don't use PHPUnit assertions in Behat's own test suite#1872carlos-granados wants to merge 2 commits into
carlos-granados wants to merge 2 commits into
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
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.
First step towards #1746: neither our FeatureContext nor the fixture contexts use PHPUnit assertions any more, so that core can later drop PHPUnitExceptionStringer without breaking our tests. The fixtures now use a small
Behat\Tests\Fixtures\Asserthelper that keeps the existing message wording.The failures on PHP 8.4 and 8.5 are unrelated to this change: #1873 needs to be merged and this branch rebased before all tests pass.