mgr/dashboard: Maintain and improve code coverage on dashboard PRs
Find github plugins or extend Jenkins to enforce a test coverage that cannot decrease.
Best would be on a per file basis for unit tests.
Currently no idea how to measure E2E and API tests, may be there is a way.
#7 Updated by Stephan Müller about 2 years ago
The current problem is that codecov and codacy need a git hub token to be send with the coverage reports.
They both suggest using CircleCI or TravisCI to export the variable as a secret. We have Jenkins in place, but I currently see no way to use the token as a secret to upload the coverage reports even if some Jenkins administrator would create the environment variable, someone could just echo it out in a PR and steal it (or am I wrong here?).
I will investigate further.
#8 Updated by Stephan Müller about 2 years ago
I found a solution for the problem which is described here: https://www.tikalk.com/posts/2017/03/07/how-to-mask-credentials-in-your-jenkins-jobs/
There is a plugin for Jenkins to use credentials in way that they can't be exposed if someone tries it will print out some asterisks instead.
The only problem now is to find an admin in charge to do that for us.
Does anybody know who can help us out here?
#11 Updated by Ernesto Puerta about 2 years ago
Ooops. My PR on refactoring unit-tests is currently blocked as I'm modifying the behaviour of install-deps.sh script and need agreement/inputs on these changes. However, as this change needs mine, I may refactor mine to leave just the things you need here (mocking + disable doctests). How does it sound?