Repository navigation
Issue/622 Address the review findings of the PHPUnit 10 upgrade - #636
Merged
Merged
Conversation
…hes with CodeRabbit Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
…it.xml Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.
Follow-up to #632 for #622. This pull request targets
3.1.x, so it does not close the issue; the merge of3.1.xintomasterdoes.What changed
phpunit.xml:failOnWarningandfailOnRiskyare on, so a warning or a risky test fails the run without relying on the CI flags.tests/Unit/Tracer/ErrorHandlerTest.php: removed thetearDown()override that repeated the handler restore already done inAppTestCase::tearDown(). The two tests that callErrorHandler::setup()now remove the handlers they register themselves..coderabbit.yaml: CodeRabbit also reviews pull requests into maintenance branches (3.1.x,3.2.x, ...), not only the default branch.Why
CodeRabbit reviewed #632 only in the merge of
3.1.xintomaster, because it skips pull requests into other branches. These are the two valid findings from that review, and the config makes later reviews happen in the pull request of the change.Breaking changes
None. Only test configuration and tests change.
Testing
ErrorHandlerTest: every test now leaves the error and exception handler stacks as it found them (20 of 22 did not before).failOnWarningandfailOnRisky, a test that emits a warning or has no assertion makes PHPUnit exit with 1; before it exited with 0.Notes for reviewers
--fail-on-warning --fail-on-risky; that is now redundant and left unchanged.3.1.x.