![]() You also need Code Mappings to be set up for your GitHub integration. You just need to have the GitHub integration for Sentry installed and have your test coverage data in Codecov to start using this integration. Note: “Single-player mode” for 1 developer is free for Sentry and Codecov, alike. After some napkin math, that works out to ~50% off our current offering. ![]() To help get you started with code coverage in Sentry, we created a new offer exclusively for Sentry customers where they get 5 seats of Codecov Pro for $29/month. With the Sentry and Codecov integration, I no longer have to analyze our codebase and spend cycles thinking about where we need test coverage, instead, Sentry just tells me exactly where I need to focus - saving me several weeks out of my year and reducing my time spent on building test coverage by nearly 50%.Īlex Nathanail, Director of Technology .uk Improving our test coverage has meant dedicating a “coverage week” every few months to improve tests in places I think are important. With Codecov in Sentry, you can pinpoint exactly where you need to prioritize adding coverage so you can maintain reliable code without sacrificing developer velocity or productivity. No more dedicated coverage reviews, thinking through the different user paths, or analyzing your codebase. In one sentence: Using Codecov’s integration with Sentry allows you to see the untested code causing errors directly in the Sentry Issue stack trace. With Codecov in the Sentry stack trace, this is our first foray into unifying those data siloes pre-production and post-deploy, making it faster and easier to debug and patch problems as they come up.
0 Comments
Leave a Reply. |