You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment, it is not clear to me as a contributor which parts of the code that I am contributing are covered by tests, so I don't know if can safely change things or if I'm silently breaking something. I guess the same goes for pull request reviewers.
It would be convenient to
Explain in the contribution guidelines how to generate code coverage metrics
Use a code coverage service that reports code coverage (changes) on every pull request. Popular examples of such services are Codecov and Coveralls
@SciTools/iris-devs Is this something you have considered before? Does it sound interesting?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
At the moment, it is not clear to me as a contributor which parts of the code that I am contributing are covered by tests, so I don't know if can safely change things or if I'm silently breaking something. I guess the same goes for pull request reviewers.
It would be convenient to
@SciTools/iris-devs Is this something you have considered before? Does it sound interesting?
Beta Was this translation helpful? Give feedback.
All reactions