[wp-trac] [WordPress Trac] #53010: Tests: introduce namespacing for the test classes
WordPress Trac
noreply at wordpress.org
Tue Jul 8 17:57:52 UTC 2025
#53010: Tests: introduce namespacing for the test classes
--------------------------------------+------------------------------------
Reporter: jrf | Owner: hellofromTonya
Type: task (blessed) | Status: assigned
Priority: normal | Milestone: Future Release
Component: Build/Test Tools | Version:
Severity: normal | Resolution:
Keywords: has-patch has-unit-tests | Focuses: docs, coding-
| standards
--------------------------------------+------------------------------------
Comment (by johnbillion):
I share the concerns of @azaozz about the extraordinary maintenance burden
that's placed on the maintainers of an existing test codebase with each
new release of PHPUnit, coupled with the narrowly supported range of PHP
versions (although this is mitigated with the PHPUnit-Polyfills library
that's in use).
I would go as far as saying that I think the continued use of PHPUnit
represents a maintainability risk for the WordPress project if there are
breaking changes in each year's new release. The maintainer of PHPUnit is
free to manage the project as they see fit, but it doesn't seem to fit
with the way that the WordPress project is managed.
* Does supporting PHPUnit 12 really require such a huge code churn so we
can take advantage of approximately zero new features?
* How can we make the required changes in a manageable fashion?
* Are the file and test renaming are only required for improved coverage
reporting? If so, can it be done piecemeal?
* If test classes need to be split up, how can they practically be
reviewed at scale? WordPress has 25,000 tests across 900 test classes.
* Can we rely on the continued maintenance of PHPUnit-Polyfills?
--
Ticket URL: <https://core.trac.wordpress.org/ticket/53010#comment:54>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list