WordPress.org

Make WordPress Core

Opened 4 months ago

Last modified 3 months ago

#46373 new task (blessed)

Add code coverage tracking

Reported by: pento Owned by:
Milestone: 5.3 Priority: normal
Severity: normal Version:
Component: Build/Test Tools Keywords:
Focuses: Cc:

Description

To help track what we're testing, code coverage is useful.

Let's investigate the services that can provide this.

Attachments (1)

46373.diff (3.6 KB) - added by pento 4 months ago.

Download all attachments as: .zip

Change History (6)

@pento
4 months ago

#1 @pento
4 months ago

46373.diff gets codecov (kind of) working.

There are some unit test failures when it runs, though: https://travis-ci.org/WordPress/wordpress-develop/jobs/499749838

Results: https://codecov.io/gh/WordPress/wordpress-develop/branch/try%2Fcodecov

@whyisjake, @joyously: y'all were going to look at this, here's a starting point. You should be able to connect services to your personal GitHub accounts for testing, but let me know if you need something connected to the WordPress organisation.

#2 @whyisjake
4 months ago

Accidentally started on this yesterday with a PR to core...

https://github.com/WordPress/wordpress-develop/pull/42

Thanks for kicking this off @pento.

#3 @johnbillion
3 months ago

Coverage reports in PHPUnit require Xdebug, which we disable on Travis for performance reasons. Do these coverage reports actually work?

#4 @pento
3 months ago

46373.diff uses phpdbg instead of xdebug, because it's a whole lot faster.

#5 @jorbin
3 months ago

  • Milestone changed from 5.2 to 5.3

I’m removing from 5.2, but if there is traction this could come back in as a tool chain request like this can happen at just about any time.

Note: See TracTickets for help on using tickets.