You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
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.
The text was updated successfully, but these errors were encountered: