Problem/Motivation

PHPUnit 11.5.24 introduced separate logic to let the test fail on warnings thrown by PHPUnit itself (i.e. not via a trigger_error() call). Very similar to the logic for PHPUnit own deeprecations.

Not setting the attribute leads to PHPUnit warnings not being reported nor fail the test runs.

Proposed resolution

Add the failOnPhpunitWarning="true" attribute to thePHPUnit xml configuration file.

Remaining tasks

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet

Issue fork drupal-3543969

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

mondrake created an issue. See original summary.

mondrake opened merge request !13120

mondrake’s picture

mondrake
Location 🇮🇹
commented
Status: Active » Needs review
smustgrave’s picture

smustgrave commented
Status: Needs review » Reviewed & tested by the community

No objections

catch’s picture

catch
he/him
Primary language English
commented
Status: Reviewed & tested by the community » Fixed

Committed/pushed to 11.x, thanks!

Now that this issue is closed, please review the contribution record.

As a contributor, attribute any organization helped you, or if you volunteered your own time.

Maintainers, please credit people who helped resolve this issue.

catch closed merge request !13120

  • catch committed 64aa0d9b on 11.x 
    Issue #3543969 by mondrake: Add failOnPhpunitWarning attribute to...

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.