Hi Ivan,
I don't have any experience with the sites but I wouldn't mind trying
out one of these. As far as I understand they help to visualize code
coverage and perform static analysis to find code problems. As for the
code coverage, we have to build in coverage checks into our build
system oursel
+1Indeed we should pay attention to the code quality.The confused
module list also need better design.
At 2016-08-31 22:37:35, "Ivan Mushketyk" wrote:
>Hi!
>
>Flink uses Travis and Jenkis to check if new PR passes unit tests, but
>there are other tools that can automatically check code quality
Hi!
Flink uses Travis and Jenkis to check if new PR passes unit tests, but
there are other tools that can automatically check code quality like:
https://www.codacy.com/
https://codeclimate.com/
These tools promise to track test coverage, check code style, detect code
duplication and so on.
Since
