[wp-trac] [WordPress Trac] #53010: Tests: introduce namespacing for the test classes
WordPress Trac
noreply at wordpress.org
Wed Jul 9 19:45:59 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 pbearne):
Replying to [comment:54 johnbillion]:
We need tests, if not PHPUnit, then what?
If we don't update, we might not be able to update the version of PHP used
I believe we can do the migration, but it will need a team to tackle it
outside of the main core team
We create a new protected branch as a pull target, and we first merge into
this branch.
The team is allowed to merge into the new branch (after three team members
have approved the pull request).
Then a core committer (or we add a guest committer) merges this into trunk
after only checking that NO changes were made outside the test folders and
no error in the test suite (this reduces the load on the core team)
We need to enable the team to do the work and get out of the way
Have thought about how to migrate the tests. I would like to suggest
creating a new folder
tests/phpunit11, and we move the tests to this new location. This way we
can duplicate all the workflows on GitHub to run both the current PHPunit
and PHPunit11 while keeping them separate.
This will help the team to track what has been done and allow commits in
the old folder while we are migrating
--
Ticket URL: <https://core.trac.wordpress.org/ticket/53010#comment:55>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list