Code Coverage for Developers
Check and correct code coverage before release in your code host, and find it in the stack trace when things get real.
Aggregate coverage reporting, see changes over time, and get cross-repo analytics so you have visibility across all your services.
Create custom statuses and group coverage in your repo without modifying your test setup using Flags and Components.
Getting started with Sentry is simple
We support every technology (except the ones we don't).
Get started with just a few lines of code.
Just run this commmand to sign up for and install Sentry.
npx @sentry/wizard@latest -i nextjs
Enable Sentry Tracing by adding the below code.
import * as Sentry from '@sentry/nextjs'; Sentry.init({ dsn: 'https://examplePublicKey@o0.ingest.sentry.io/0', // We recommend adjusting this value in production, or using tracesSampler // for finer control tracesSampleRate: 1.0, });
That's it. Check out our documentation to ensure you have the latest instructions.
FAQs
You must be on a Sentry Team or Business plan - check your Sentry plan subscription. Additionally, make sure you have Sentry’s GitHub integration installed and Code Mappings configured. This will help Sentry determine which source code files to fetch for coverage information.
Codecov Requirements
You must be an existing Codecov customer. If you’re not, getting started with Codecov takes a few minutes and you can try it for free for 14 days. Sign up here.
There is a direct correlation between poor test coverage and incidents.
Code coverage is a testing technique that informs what code is tested and what is not. It is often represented as a percentage of the number of lines of code tested versus the entire codebase. Without building these tests and having proper test coverage, it’s easy to miss preventable bugs before shipping to production which impacts the user experience and can have your developers scrambling to find fixes.
With code coverage solutions like Codecov, you can get a holistic view of your code coverage so you can do things like understand what code is covered when there are drops in code coverage. You can provide blocking status checks on PRs to prevent merging code that has not been well-tested so you and your team can build more reliable and secure code.
To learn more, check out Codecov’s free ebook.
Of course we have more content
Get monthly product updates from Sentry
Sign up for our newsletter.
And yes, it really is monthly. Ok, maybe the occasional twice a month, but for sure not like one of those daily ones that you just tune out after a while.
Fix it
Get started with the only application monitoring platform that empowers developers to fix application problems without compromising on velocity