Move code coverage from Travis to Scrutinizer #6556
Labels
c: Tests & QA
For issues related to automated tests or making it easier to QA & test issues.
Task
Indicates an issue is neither a feature nor a bug and it's purely a "technical" change.
Milestone
We have enabled Scrutinizer for Piwik. This CI tools mainly does code quality inspections, which includes the classic ones (pdepend, copy paste detector, …) but also a proprietary one they have developed which is pretty powerful and useful.
Scrutinizer also offers to run tests and code coverage reports. For now I have set up code coverage for unit tests only: https://scrutinizer-ci.com/g/piwik/piwik
The goal is to remove code coverage completely from Travis so that builds are even faster.
I think we should not have code coverage for integration tests. If we agree on that, then we just have to remove code coverage in the Travis build.
If we decide to keep code coverage for integration tests, then we need to configure them on Scrutinizer, then we can remove them from Travis.
So should we have code coverage for integration tests?
The text was updated successfully, but these errors were encountered: