Codecov

Write comment, get tests: AI Test Generation is now in your PR. - Codecov Sometimes you just need to merge. Maybe a critical bug is breaking production. Maybe sales promised a feature that definitely didn’t exist yet and it’s blocking the largest deal of ...

Write comment, get tests.

AI Test Generation is now in your GitHub PR comment. Breeze through code coverage gates without writing a single test or even leaving your PR. Learn more in our latest blog.

bit.ly/43FwQ0a

Badges provide a quick view of important information about your repo, and we just added a new one. Now you can add a bundle size badge to your repo’s README. docs.codecov.com/docs/status-...

How I boosted test suite speed by 10% in under an hour - Codecov Maintaining a test suite is like a slow-moving game of Tetris. If you stay on top of it, fixing one slow or flaky test here or there is easy, and ...

Our own Ajay Singh turned a spare hour on a Friday afternoon into a 10% reduction in test suite run time for his whole team. Here are the tools he used: bit.ly/3E6XWn6

Monitoring JavaScript Bundle Size Changes in Remix - Codecov This is a guest post from Artem Zakharchenko, creator of MSWJS, an API mocking library for Javascript. He also writes about testing for EpicWeb and on his personal blog. Performance ...

If you want a faster website, serve less code.

@kettanaito.com shares his favorite performance-boosting tools and APIs in his latest blog.

Happening tomorrow 👇

@kettanaito.com breaks down why you should get a head of flaky tests -- "A test you cannot trust is a useless test."

Fun Fact: Codecov now alerts you of flaky tests. How convenient is that?

about.codecov.io/blog/catchin...

Codecov is more than just test coverage. We can now tell you when to ignore flaky tests, give you a heads up on the overall health of your test suite, and automate mundane tasks with by automatically generating unit tests for you.

Find failing and flaky tests with Codecov Test Analytics - Codecov No one likes digging through logs to figure out why a test failed. Even less fun: wasting time on flaky tests. That’s why we made Test Analytics – a new ...

If it takes you longer than 30 seconds to find out why the latest test run on your pull request failed, you’re needlessly banging your head against the wall.

You need to read this...

ICYMI we have now a dark mode 😎 but if you want to learn more about our design process, you should check out this oddly nerdy post from our design team
sentry.design/blog/codecov...

ou may not need all that, or you may not feel like signing up for Codecov. Either way we still don’t want you dumpster diving. So go ahead and try the Basic Test Results GitHub.

github.com/marketplace/...

Yeah, this capability is also built into our product, along with flaky test detection and insights to help you improve your test suite longer-term, but…

Basically, dumpster diving through CI logs for test failures sucks. We don’t think anyone should have to do it. Especially when the failed test and stack trace could just be a PR comment.

We created a free, open access GitHub Action for a failed test detection capability you could get by signing up for Codecov. Why? 🧵