-
Notifications
You must be signed in to change notification settings - Fork 10.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PhpUnit now throws warnings: Test code or tested code removed exception handlers other than its own #50951
Comments
Hey there, thanks for reporting this issue. We'll need more info and/or code to debug this further. Can you please create a repository with the command below, commit the code that reproduces the issue as one separate commit on the main/master branch and share the repository here? Please make sure that you have the latest version of the Laravel installer in order to run this command. Please also make sure you have both Git & the GitHub CLI tool properly set up.
Do not amend and create a separate commit with your custom changes. After you've posted the repository, we'll try to reproduce the issue. Thanks! |
I'm sorry - I don't have time. However, the previous post offered these commands. laravel new laravel |
I am also getting this on a new Laravel 11 project |
This also happens on Symfony 7.0.3 controller tests |
@driesvints is this being looked at? It's not a closed issue. |
I need a way to reproduce this. |
Ok, Ill look at trying to make a suitble test later today. |
If (The call to |
Read the Caveat section from https://tighten.com/insights/tidying-up-your-phpunit-tests-with-data-providers/ |
Laravel Version
11.2.0
PHP Version
8.3
Database Driver & Version
MySql 8
Description
As per issue: #49502
When running tests, the vast majority produce the warning: "Test code or tested code removed exception handlers other than its own"
This seems to have been a short lived change in PhpUnit that was reverted... I think it's back now!
Steps To Reproduce
.. use any repo with existing tests OR:
Install L11.
Run a test on a view using something like $response->assertStatus(200);
The text was updated successfully, but these errors were encountered: