[wp-trac] [WordPress Trac] #53010: Tests: introduce namespacing for the test classes

WordPress Trac noreply at wordpress.org
Wed Sep 18 20:32:40 UTC 2024


#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:  2nd-opinion has-patch has-unit-      |     Focuses:  docs,
  tests                                          |  coding-standards
-------------------------------------------------+-------------------------

Comment (by hellofromTonya):

 == Scope of Work that can start now

 The required changes for #62004 are:

 1. For tests that include more than one function or method, split each
 function and method into a separate test class and file.
 2. Rename each test class.
 3. Rename each test file to exactly match the test class name.

 Contributors:
 Work can (and should) start on doing only this part of the scope.
 Currently, there are PRs/patches you can use as examples, such as
 https://github.com/WordPress/wordpress-develop/pull/6235.

 == Scope of Work that is still being discussed

 What about the remaining parts of the proposal?
 * Namespace.
 * Reorganize the test suite directory and file structure.

 Currently, there's not ''yet'' consensus on these remaining parts.

 Contributors:
 Please don't yet make these changes in the PRs submitted.

 == Committers

 Ideally, consensus is reached on the remaining parts of this proposal
 before the commits are done. Why? To touch the files once and minimize the
 impacts to existing patches/PRs.

 Let's work towards getting consensus on whether to move or not with the
 remaining parts of the proposal (i.e. namespace and directory
 reorganization).

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


More information about the wp-trac mailing list