[wp-trac] [WordPress Trac] #26999: Improve the layout of phpunit unit tests to gauge code coverage

WordPress Trac noreply at wordpress.org
Fri Jan 9 01:43:27 UTC 2015


#26999: Improve the layout of phpunit unit tests to gauge code coverage
------------------------------------------+-----------------------------
 Reporter:  wonderboymusic                |       Owner:
     Type:  enhancement                   |      Status:  new
 Priority:  normal                        |   Milestone:  Future Release
Component:  Build/Test Tools              |     Version:
 Severity:  normal                        |  Resolution:
 Keywords:  needs-patch needs-unit-tests  |     Focuses:
------------------------------------------+-----------------------------

Comment (by sgrant):

 What about refactoring the unit test file layout to match the phpunit
 filesystem recommendation?

 https://phpunit.de/manual/current/en/organizing-tests.html

 I'm also finding it difficult in some cases, especially as a relatively
 new contributor, to figure out the best location for new tests. Would
 there be a benefit to restructuring the suite to match the layout of the
 source it's testing? (see attached patch for simple examples that add
 @covers notation and move to a wp-* layout; the real benefit might be
 taking something like the formatting directory and organizing tests by
 source file instead of by ticket/test concept).

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


More information about the wp-trac mailing list