[wp-trac] [WordPress Trac] #54183: Tests: decide on how to handle deprecations in PHPUnit

[WordPress Trac]

#54183: Tests: decide on how to handle deprecations in PHPUnit
--------------------------------------------+-----------------------------
 Reporter:  jrf                             |       Owner:  SergeyBiryukov
     Type:  task (blessed)                  |      Status:  assigned
 Priority:  normal                          |   Milestone:  Future Release
Component:  Build/Test Tools                |     Version:
 Severity:  normal                          |  Resolution:
 Keywords:  php81 has-patch has-unit-tests  |     Focuses:
--------------------------------------------+-----------------------------

Comment (by SergeyBiryukov):

 Replying to [comment:8 SergeyBiryukov]:
 > Replying to [comment:5 costdev]:
 > > **Option 3**
 > > This is the best option IMHO, but requires some work to resolve risky
 tests in Core.
 > >
 > > We could do a review of risky tests to get an idea of the work
 involved in implementing Option 3. Until it's implemented, I'd suggest
 that we implement Option 2 as soon as possible to prevent any deprecations
 making their way into Core.
 >
 > I tend to agree. I've been meaning to review those risky tests for a
 while :)

 Just noting that empty REST API tests previously marked as risky were
 addressed in [53921] and [54058] / #41463.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54183#comment:32>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform