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

[WordPress Trac]

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

Comment (by bpetty):

 Generally speaking, I figured we were just headed down the road of
 organizing them by the same new component tree we have in Trac. They are
 mainly organized like this already, though you're right, they still need a
 lot more cleanup. It's already very difficult to traverse the code history
 on unit tests since it was merged from the unit-tests repo, we should try
 to avoid moving mass amounts of code even more.

 As far as figuring out what level of coverage there is, that's what code
 coverage tools are for. We don't necessarily need to break the unit tests
 out to a one-to-one file match based on how the core code is organized.

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