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.

Sign up for GitHub

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

Jump to bottom

Setup Coveralls for Piwik Code coverage report #4302

Closed
mattab opened this issue Nov 14, 2013 · 5 comments
Closed

Setup Coveralls for Piwik Code coverage report #4302

mattab opened this issue Nov 14, 2013 · 5 comments
Assignees
@sgiehl
Labels
Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change.

Comments

@mattab
Copy link
Member

mattab commented Nov 14, 2013

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
Copy link
Member Author

mattab commented Jan 3, 2014

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

@mattab mattab added this to the Future releases milestone Jul 8, 2014
@sgiehl sgiehl self-assigned this Aug 17, 2014
sgiehl pushed a commit that referenced this issue Aug 20, 2014
Merge pull request #6023 from sgiehl/master
4c7e446 
refs #4224, #4302 - added code coverage report using coveralls.io
@sgiehl
Copy link
Member

sgiehl commented Sep 10, 2014

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.

@sgiehl sgiehl closed this as completed Sep 10, 2014
@mattab
Copy link
Member Author

mattab commented Sep 11, 2014

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 🎱 for adding coverage to Piwik!

@mattab
Copy link
Member Author

mattab commented Sep 11, 2014

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

@sgiehl sgiehl mentioned this issue Sep 11, 2014
Closed
@mattab mattab mentioned this issue Oct 10, 2014
Closed
@mattab mattab mentioned this issue Mar 9, 2015
Closed
@Selena20191
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sgiehl sgiehl

Labels
Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mattab @sgiehl @Selena20191