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.
Join the Sentry and Codecov (by Sentry) engineers, Dhrumil, Eli, Tom, and Snigdha, as they dive into the integration to share how you can see where your code is missing coverage - or where your tests might not be working as intended.
In this session you’ll get:
Sign up and add in your questions now to get them answered during the session. Can’t make it? Don’t worry, register anyway and we’ll send you the replay.
Senior Product Manager Sentry Sentry
Head of Engineering at Codecov Codecov @ Sentry Sentry
Devloper Advocate Codecov @ Sentry Sentry
Software Engineer Sentry Sentry
Here’s a quick look at how Sentry handles your personal information (PII).×
We collect PII about people browsing our website, users of the Sentry service, prospective customers, and people who otherwise interact with us.
What if my PII is included in data sent to Sentry by a Sentry customer (e.g., someone using Sentry to monitor their app)? In this case you have to contact the Sentry customer (e.g., the maker of the app). We do not control the data that is sent to us through the Sentry service for the purposes of application monitoring.Am I included?
We may disclose your PII to the following type of recipients:
You may have the following rights related to your PII: