AMA: Achieving code reliability across the release cycle
Code coverage, arguably a very important measure that we as development teams don’t pay enough attention to. That is until Sentry notifies you of a frustrating/critical/oh s*#t moment. Then we all think: “how could this have been avoided?”, “why didn’t our tests catch it?”, “oh… we didn’t have any coverage on this flow.” With our new Codecov integration, you can avoid regressions (and awkward conversations) by being able to see which lines that caused an issue are covered and which ones are not - right in the stack trace we kick out on every error report.