Choose code quality/coverage tool?

[jvdzwaan]

The guide specifies three code quality/coverage tools: codacy, Scrutinizer, and Landscape, but does not make a recommendation.

Do we recommend one? If so, which one? I have only used codacy, so I can't really recommend anything else...

[jhidding]

I'm using CodeCov mainly. Got fed up with codacy. The main issue is that these tools should fit with our idea of code quality. This ties in with which linter to use. To me Flake8 gives sensible output as it only checks basic formatting rules, but pylint is way to pedantic and it doesn't understand decorators or higher order programming all to well. The metrics that remain important in my opinion are documantion and testing coverage.

[sverhoeven]

I use SonarCloud for coverage eg. https://sonarcloud.io/component_measures?id=experiment-launcher&metric=coverage, SonarCloud also offers linting using quality profile

[LourensVeen]

I use Codacy as well, and I like it's GUI. You can easily browse issues, and disable specific issues or specific rules, and it gives some nice statistics. My main gripe with it is that it's slow, but well, gift horses and all...

[fdiblen]

Created two other issues for this: #88 #89.