@mattab opened this Issue on November 14th 2013 Member

Follow up of: #4224

Once we have the technology to generate proper coverage (see #4224) it would be nice to setup automatic reporting of code coverage eg. once a day.

Coveralls service looks very interesting, let's try it!
https://coveralls.io/r/piwik/piwik

@mattab commented on January 3rd 2014 Member

Not sure if this is do-able since it would need huge memory (+2Gb to generate full coverage report)

@sgiehl commented on September 10th 2014 Member

Guess we can close the for now. Coveralls.io is running for Piwik. There may still be some more improvements/adjustments we could make, but we should create new tickets or reopen that one as soon as they occur.

@mattab commented on September 11th 2014 Member

Well done @sgiehl - this is a great long term investment in raising the project testing culture!
we'll need some time to use the reports and see how well covered the core modules are. It will be so useful as we try to break down our big integration tests in smaller tests.

Maybe you could create an issue for a follow up to implement code coverage for plugins? eg. we could add this feature to the default plugin template that is used when calling ./console generate:test

Otherwise :8ball: for adding coverage to Piwik!

@mattab commented on September 11th 2014 Member

Check out the code coverage report here: https://coveralls.io/r/piwik/piwik

@Selena20191 commented on January 3rd 2022
This Issue was closed on September 10th 2014
Powered by GitHub Issue Mirror