WordPress.org

Make WordPress Core

Opened 4 years ago

Closed 4 years ago

#33838 closed task (blessed) (fixed)

Add a config for Coveralls

Reported by: wonderboymusic Owned by: jorbin
Milestone: 4.4 Priority: normal
Severity: normal Version:
Component: Build/Test Tools Keywords:
Focuses: Cc:
PR Number:

Description

We should try to use Coveralls for Test Coverage:
https://coveralls.io/

Change History (7)

#1 @wonderboymusic
4 years ago

  • Owner set to jorbin
  • Status changed from new to assigned

#2 follow-up: @johnbillion
4 years ago

  • Version trunk deleted

We should try some actual CI. Can we get this set up on the WordPress/WordPress repo on GitHub instead of having to rely on Aaron's fork?

Also, the WP REST API recently switched from Coveralls to Codecov, but I don't think it was for any reason other than needing to use a branch other than master as the default branch.

#3 @pento
4 years ago

@nacin is going to be looking at fixing the WordPress/WordPress repo on GitHub soon, so we can use GH integrations from there instead.

#4 in reply to: ↑ 2 @netweb
4 years ago

Replying to johnbillion:

We should try some actual CI. Can we get this set up on the WordPress/WordPress repo on GitHub instead of having to rely on Aaron's fork?

Code Climate is using that repo https://codeclimate.com/github/WordPress/WordPress, but they do things a little different, anyone can add a "public" repo e.g. https://codeclimate.com/github/WP-API/WP-API and the results are public.

Nacin's going to fix this, because he said "gonna" ;) https://twitter.com/nacin/status/635314769550028800

Also, the WP REST API recently switched from Coveralls to Codecov, but I don't think it was for any reason other than needing to use a branch other than master as the default branch.

I believe this was primarily because Coveralls could not use a default branch other than master which was a problem for pull requests.

Either way, at the moment we're going to add Code Climate and Coveralls for starters to evaluate which is best for our use case, I've already done Codecov previously which we can also look at by the way https://codecov.io/github/ntwb/wordpress

This ticket was mentioned in Slack in #core by wonderboymusic. View the logs.


4 years ago

#6 @rmccue
4 years ago

Now that we've used it on the API for a bit, Codecov is actually a bit better of a tool. Coveralls often has problems with percentages not staying constant with the same set of code, Codecov seems to do a better job.

#7 @jorbin
4 years ago

  • Resolution set to fixed
  • Status changed from assigned to closed

Codecov - https://codecov.io/github/aaronjorbin/wordpress.codecov
Coveralls - https://coveralls.io/github/aaronjorbin/wordpress.codecov

Both of these are run once an hour if there have been commits in the last hour. If we move more infrastructure over to github, we can revisit how these are generated, but I'm going to close this for 4.4 as done in the meantime.

The sync script and alternative .travis.yml are located at: https://github.com/aaronjorbin/develop-sync

For some explanation on why there is a separate repo with a separate .travis.yml, see https://daily.jorb.in/2015/10/23/automated-code-coverage-of-wordpress-core-php-code/ (essentially it comes down to time)

Note: See TracTickets for help on using tickets.