[wp-trac] [WordPress Trac] #59486: Make test suite compatible with PHPUnit 10 / 11

[WordPress Trac]

#59486: Make test suite compatible with PHPUnit 10 / 11
------------------------------+-----------------------------
 Reporter:  dingo_d           |       Owner:  (none)
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:  Future Release
Component:  Build/Test Tools  |     Version:  6.4
 Severity:  normal            |  Resolution:
 Keywords:  close             |     Focuses:
------------------------------+-----------------------------
Changes (by hellofromTonya):

 * keywords:  needs-patch => close


Comment:

 **Status Update:**

 Thank you @vphrudy for the ping in the Making WordPress `#core` slack
 channel.

 As @jrf [comment:7 noted]:
 >There is much bigger problem we have to deal with before this could be
 contemplated (complete reorganization of the test suite). I don't think
 adding my analysis in a comment in this ticket is the right way forward,
 so I propose I open a new ticket with a detailed analysis and roadmap to
 replace this ticket.

 [https://wordpress.slack.com/archives/C02RQBWTW/p1719580661959029?thread_ts=1719578755.249109&cid=C02RQBWTW
 Juliette has drafted an epic] (bigger picture proposal) ticket for this
 initiative. The initiative is currently blocked by solving the
 "deprecation expectation thingie":
 >(and yes, the deprecation expectation thingie is the blocker for the
 release - I'm still trying to figure out a way to polyfill that, though
 3.0 might just end up not supporting PHPUnit 10 (which would bypass the
 problem))

 Getting WordPress Core running on PHPUnit 11.1 will require significant
 changes and challenges to solve:
 * Core's entire test suite will require rearchitecting and reorganization
 (reasonings will be shared in the epic ticket).
 * Handling of "deprecation expectation thingie" is a hard challenge, one
 that will be solved as part of PHPUnit Polyfills 3.0 (that will have
 PHPUnit 11 support).

 The current plan:
 * Close this ticket in favor of the new epic ticket (I added `close`
 keyword).
 * The new epic ticket will track the bigger picture of the proposal and
 initiative. Individual tasks will then have their own tickets for tracking
 their specific (smaller) scope of work and discussions.
 * WP will support PHPUnit 8, 9 and 11.1+, skipping PHPUnit 10 and 11.0
 (reasons will be shared in the epic ticket).
 * Tests suite's rearchitecture and reorganization task will be tracked in
 its own ticket and can happen in tandem. (Early work PRs are available,
 though waiting on the proposal before moving them into a ticket and out of
 draft.)

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