Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unit testing: add clover coverage? #342

Open
netsensei opened this issue Oct 3, 2015 · 3 comments
Open

Unit testing: add clover coverage? #342

netsensei opened this issue Oct 3, 2015 · 3 comments

Comments

@netsensei
Copy link
Contributor

Clover coverage is supported by PHPUnit. I use it an several other projects. It reports how well unit tests are covering the actual code. It helps tremendously to write tests more efficiently because you can see what parts of the code are tested and which aren't.

Clover coverage also integrates nicely with Jenkins and I've noticed that it also shows up in the build logs in Travis.

@netsensei
Copy link
Contributor Author

Requirements: you will need xdebug enabled for php-cli.

@netsensei
Copy link
Contributor Author

Just ran phpunit with clover coverage: report attached.

I did notice that running phpunit includes running all tests: including tests provided by Laravel and all dependent vendor packages. With clover coverage on, it took over 10 minutes to run all the tests. So we probably want to figure out how to reduce this so that only app specific code is tested.

screen shot 2015-10-03 at 19 24 00

@coreation
Copy link
Member

Hey @netsensei thanks for the elaborate report, to be honest we know our tests aren't 100% sufficient, we only provided tests for our most important functionalities. Will look into it and see if the clover coverage marks any important functionalities.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants