#codecoverage — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #codecoverage, aggregated by home.social.
-
From the Visual Studio blog...
In case you missed it earlier...
Today I will… improve test coverage
https://devblogs.microsoft.com/visualstudio/today-i-will-improve-test-coverage/ #CodeCoverage #Copilot #Productivity #Testing -
From the Visual Studio blog...
In case you missed it earlier...
Today I will… improve test coverage
https://devblogs.microsoft.com/visualstudio/today-i-will-improve-test-coverage/ #CodeCoverage #Copilot #Productivity #Testing -
From the Visual Studio blog...
In case you missed it earlier...
Today I will… improve test coverage
https://devblogs.microsoft.com/visualstudio/today-i-will-improve-test-coverage/ #CodeCoverage #Copilot #Productivity #Testing -
From the Visual Studio blog...
In case you missed it earlier...
Today I will… improve test coverage
https://devblogs.microsoft.com/visualstudio/today-i-will-improve-test-coverage/ #CodeCoverage #Copilot #Productivity #Testing -
From the Visual Studio blog...
Today I will… improve test coverage
https://devblogs.microsoft.com/visualstudio/today-i-will-improve-test-coverage/ #CodeCoverage #Copilot #Productivity #Testing -
From the Visual Studio blog...
Today I will… improve test coverage
https://devblogs.microsoft.com/visualstudio/today-i-will-improve-test-coverage/ #CodeCoverage #Copilot #Productivity #Testing -
From the Visual Studio blog...
Today I will… improve test coverage
https://devblogs.microsoft.com/visualstudio/today-i-will-improve-test-coverage/ #CodeCoverage #Copilot #Productivity #Testing -
From the Visual Studio blog...
Today I will… improve test coverage
https://devblogs.microsoft.com/visualstudio/today-i-will-improve-test-coverage/ #CodeCoverage #Copilot #Productivity #Testing -
Code Coverage: How to Measure It, Understand the Metrics, and Improve Your Tests, by @jetbrains.com:
https://blog.jetbrains.com/qodana/2026/07/code-coverage-tests/?ref=frontenddogma.com
-
Code Coverage: How to Measure It, Understand the Metrics, and Improve Your Tests, by @jetbrains.com:
https://blog.jetbrains.com/qodana/2026/07/code-coverage-tests/?ref=frontenddogma.com
-
Code Coverage: How to Measure It, Understand the Metrics, and Improve Your Tests, by @jetbrains.com:
https://blog.jetbrains.com/qodana/2026/07/code-coverage-tests/?ref=frontenddogma.com
-
Code Coverage: How to Measure It, Understand the Metrics, and Improve Your Tests, by @jetbrains.com:
https://blog.jetbrains.com/qodana/2026/07/code-coverage-tests/?ref=frontenddogma.com
-
An open source project just fixed a bug that I reported 14 years ago. Surprisingly for such an old bug, the bug fix is still useful to me!
https://github.com/pjcj/Devel--Cover/pull/602
Thanks @pjcj!
-
An open source project just fixed a bug that I reported 14 years ago. Surprisingly for such an old bug, the bug fix is still useful to me!
https://github.com/pjcj/Devel--Cover/pull/602
Thanks @pjcj!
-
An open source project just fixed a bug that I reported 14 years ago. Surprisingly for such an old bug, the bug fix is still useful to me!
https://github.com/pjcj/Devel--Cover/pull/602
Thanks @pjcj!
-
An open source project just fixed a bug that I reported 14 years ago. Surprisingly for such an old bug, the bug fix is still useful to me!
https://github.com/pjcj/Devel--Cover/pull/602
Thanks @pjcj!
-
How to Customize JaCoCo Report Styling in Your Java Project
#codecoverage #css #jacoco #java
https://foojay.io/today/how-to-customize-jacoco-report-styling-in-your-java-project/
-
How to Customize JaCoCo Report Styling in Your Java Project
#codecoverage #css #jacoco #java
https://foojay.io/today/how-to-customize-jacoco-report-styling-in-your-java-project/
-
How to Customize JaCoCo Report Styling in Your Java Project
#codecoverage #css #jacoco #java
https://foojay.io/today/how-to-customize-jacoco-report-styling-in-your-java-project/
-
How to Customize JaCoCo Report Styling in Your Java Project
#codecoverage #css #jacoco #java
https://foojay.io/today/how-to-customize-jacoco-report-styling-in-your-java-project/
-
Meet Covpeek - a fast, language-agnostic coverage parser that extracts coverage data across projects. No more juggling formats - unify reports and focus on quality.
Try it today: https://github.com/Chapati-Systems/covpeek
#covpeek #codecoverage #devops #coverage #testing #ci #rust #golang
-
Meet Covpeek - a fast, language-agnostic coverage parser that extracts coverage data across projects. No more juggling formats - unify reports and focus on quality.
Try it today: https://github.com/Chapati-Systems/covpeek
#covpeek #codecoverage #devops #coverage #testing #ci #rust #golang
-
Meet Covpeek - a fast, language-agnostic coverage parser that extracts coverage data across projects. No more juggling formats - unify reports and focus on quality.
Try it today: https://github.com/Chapati-Systems/covpeek
#covpeek #codecoverage #devops #coverage #testing #ci #rust #golang
-
When writing tests, i do not optimize for code coverage
I have now been on both sides of the code coverage debate. I have advocated that test suites should achieve higher code coverage. I have also advocated against using code coverage for blocking PR merges.
And fair warning: what i say next is based on my lived experience as a developer, and may not apply to all software engineering contexts.Some things i have learned to be true, over my time researching and practicing software engineering:
- You can execute the same line of code a million time without ever catching a bug in that line.
- Higher code coverage does not mean better tests.
- Code coverage can be gamed.
- Some code cannot be executed naturally in a test environment. A lot of UI and configuration code falls neatly in this category.
Given that, I have landed on a very basic philosophy around writing tests, and how code coverage factors in:
I do not optimize my test code for higher code coverage. And instead use coverage data to prioritize what i need to test and leave untested.
The coverage metric itself is not meaningful to me. I rather have only 30% code coverage if i am testing the most critical sections of the codebase. I prefer that over covering 70% of the codebase which may be peripheral to the program’s implementation.
Beyond the coverage metric itself, i am more interested in the set of lines got executed by the test. And i like to examine this data by each method or function. That tells me if the lines that I think should get executed are actually getting executed. I also use such insight to think about the program inputs i need to conjure to exercise the lines of code that are getting skipped from execution.
Indeed, that sort of analysis can be time consuming. But to me it is no different than the time I spend in investigate bugs in production code with breakpoints and step-through debuggers. I use the full set of covered (and uncovered) lines as data in gaining a deeper understanding of how my test code is working.
Personal take: Code coverage is not something that should be optimized for. It should be treated as an honest reflection of what got executed by the test(s), and what did not. That gives real insight into the inner mechanics of the test code.
#codeCoverage #programming #softwareMetrics #softwareEngineering #testing
-
When writing tests, i do not optimize for code coverage
I have now been on both sides of the code coverage debate. I have advocated that test suites should achieve higher code coverage. I have also advocated against using code coverage for blocking PR merges.
And fair warning: what i say next is based on my lived experience as a developer, and may not apply to all software engineering contexts.Some things i have learned to be true, over my time researching and practicing software engineering:
- You can execute the same line of code a million time without ever catching a bug in that line.
- Higher code coverage does not mean better tests.
- Code coverage can be gamed.
- Some code cannot be executed naturally in a test environment. A lot of UI and configuration code falls neatly in this category.
Given that, I have landed on a very basic philosophy around writing tests, and how code coverage factors in:
I do not optimize my test code for higher code coverage. And instead use coverage data to prioritize what i need to test and leave untested.
The coverage metric itself is not meaningful to me. I rather have only 30% code coverage if i am testing the most critical sections of the codebase. I prefer that over covering 70% of the codebase which may be peripheral to the program’s implementation.
Beyond the coverage metric itself, i am more interested in the set of lines got executed by the test. And i like to examine this data by each method or function. That tells me if the lines that I think should get executed are actually getting executed. I also use such insight to think about the program inputs i need to conjure to exercise the lines of code that are getting skipped from execution.
Indeed, that sort of analysis can be time consuming. But to me it is no different than the time I spend in investigate bugs in production code with breakpoints and step-through debuggers. I use the full set of covered (and uncovered) lines as data in gaining a deeper understanding of how my test code is working.
Personal take: Code coverage is not something that should be optimized for. It should be treated as an honest reflection of what got executed by the test(s), and what did not. That gives real insight into the inner mechanics of the test code.
#codeCoverage #programming #softwareMetrics #softwareEngineering #testing
-
When writing tests, i do not optimize for code coverage
I have now been on both sides of the code coverage debate. I have advocated that test suites should achieve higher code coverage. I have also advocated against using code coverage for blocking PR merges.
And fair warning: what i say next is based on my lived experience as a developer, and may not apply to all software engineering contexts.Some things i have learned to be true, over my time researching and practicing software engineering:
- You can execute the same line of code a million time without ever catching a bug in that line.
- Higher code coverage does not mean better tests.
- Code coverage can be gamed.
- Some code cannot be executed naturally in a test environment. A lot of UI and configuration code falls neatly in this category.
Given that, I have landed on a very basic philosophy around writing tests, and how code coverage factors in:
I do not optimize my test code for higher code coverage. And instead use coverage data to prioritize what i need to test and leave untested.
The coverage metric itself is not meaningful to me. I rather have only 30% code coverage if i am testing the most critical sections of the codebase. I prefer that over covering 70% of the codebase which may be peripheral to the program’s implementation.
Beyond the coverage metric itself, i am more interested in the set of lines got executed by the test. And i like to examine this data by each method or function. That tells me if the lines that I think should get executed are actually getting executed. I also use such insight to think about the program inputs i need to conjure to exercise the lines of code that are getting skipped from execution.
Indeed, that sort of analysis can be time consuming. But to me it is no different than the time I spend in investigate bugs in production code with breakpoints and step-through debuggers. I use the full set of covered (and uncovered) lines as data in gaining a deeper understanding of how my test code is working.
Personal take: Code coverage is not something that should be optimized for. It should be treated as an honest reflection of what got executed by the test(s), and what did not. That gives real insight into the inner mechanics of the test code.
#codeCoverage #programming #softwareMetrics #softwareEngineering #testing
-
via @dotnet : Supercharge Your Test Coverage with GitHub Copilot Testing for .NET
https://ift.tt/HnlU7Tg
#GitHubCopilot #NET #UnitTesting #VisualStudio #AIPoweredDevelopment #SoftwareTesting #CodeCoverage #DevCommunity #MSTest #xUnit #NUnit #TestAutomation #Soft… -
via @dotnet : Supercharge Your Test Coverage with GitHub Copilot Testing for .NET
https://ift.tt/HnlU7Tg
#GitHubCopilot #NET #UnitTesting #VisualStudio #AIPoweredDevelopment #SoftwareTesting #CodeCoverage #DevCommunity #MSTest #xUnit #NUnit #TestAutomation #Soft… -
via @dotnet : Supercharge Your Test Coverage with GitHub Copilot Testing for .NET
https://ift.tt/HnlU7Tg
#GitHubCopilot #NET #UnitTesting #VisualStudio #AIPoweredDevelopment #SoftwareTesting #CodeCoverage #DevCommunity #MSTest #xUnit #NUnit #TestAutomation #Soft… -
via @dotnet : Supercharge Your Test Coverage with GitHub Copilot Testing for .NET
https://ift.tt/HnlU7Tg
#GitHubCopilot #NET #UnitTesting #VisualStudio #AIPoweredDevelopment #SoftwareTesting #CodeCoverage #DevCommunity #MSTest #xUnit #NUnit #TestAutomation #Soft… -
What is the name of the metric for when you got 100% code coverage, but you got 2, 4, 10 tests covering each line of code. Coverage depth? It would be a nice statistic to have #codecoverage
-
What is the name of the metric for when you got 100% code coverage, but you got 2, 4, 10 tests covering each line of code. Coverage depth? It would be a nice statistic to have #codecoverage
-
What is the name of the metric for when you got 100% code coverage, but you got 2, 4, 10 tests covering each line of code. Coverage depth? It would be a nice statistic to have #codecoverage
-
What is the name of the metric for when you got 100% code coverage, but you got 2, 4, 10 tests covering each line of code. Coverage depth? It would be a nice statistic to have #codecoverage
-
#PostgreSQL Differential Code Coverage—Now Automated Daily!
Just came across a fantastic initiative by [@nbyavuz](https://github.com/nbyavuz) that I think the Postgres community will appreciate.
They’ve built a script that generates **differential code coverage** between the latest release branch (currently `REL_18_STABLE`) and `HEAD`—a great way to track what’s being tested as the codebase evolves. Even better, it’s automated via GitHub Actions and published daily as an HTML report.
Script: https://github.com/nbyavuz/postgres-code-coverage/blob/main/code_coverage.sh
Live Report: https://nbyavuz.github.io/postgres-code-coverageWhether you're contributing to Postgres or just curious about test coverage trends, this is worth a look. Kudos to the author for making this public and maintainable!
If you have thoughts or suggestions, I’m sure they’d welcome feedback.
-
#PostgreSQL Differential Code Coverage—Now Automated Daily!
Just came across a fantastic initiative by [@nbyavuz](https://github.com/nbyavuz) that I think the Postgres community will appreciate.
They’ve built a script that generates **differential code coverage** between the latest release branch (currently `REL_18_STABLE`) and `HEAD`—a great way to track what’s being tested as the codebase evolves. Even better, it’s automated via GitHub Actions and published daily as an HTML report.
Script: https://github.com/nbyavuz/postgres-code-coverage/blob/main/code_coverage.sh
Live Report: https://nbyavuz.github.io/postgres-code-coverageWhether you're contributing to Postgres or just curious about test coverage trends, this is worth a look. Kudos to the author for making this public and maintainable!
If you have thoughts or suggestions, I’m sure they’d welcome feedback.
-
#PostgreSQL Differential Code Coverage—Now Automated Daily!
Just came across a fantastic initiative by [@nbyavuz](https://github.com/nbyavuz) that I think the Postgres community will appreciate.
They’ve built a script that generates **differential code coverage** between the latest release branch (currently `REL_18_STABLE`) and `HEAD`—a great way to track what’s being tested as the codebase evolves. Even better, it’s automated via GitHub Actions and published daily as an HTML report.
Script: https://github.com/nbyavuz/postgres-code-coverage/blob/main/code_coverage.sh
Live Report: https://nbyavuz.github.io/postgres-code-coverageWhether you're contributing to Postgres or just curious about test coverage trends, this is worth a look. Kudos to the author for making this public and maintainable!
If you have thoughts or suggestions, I’m sure they’d welcome feedback.
-
#PostgreSQL Differential Code Coverage—Now Automated Daily!
Just came across a fantastic initiative by [@nbyavuz](https://github.com/nbyavuz) that I think the Postgres community will appreciate.
They’ve built a script that generates **differential code coverage** between the latest release branch (currently `REL_18_STABLE`) and `HEAD`—a great way to track what’s being tested as the codebase evolves. Even better, it’s automated via GitHub Actions and published daily as an HTML report.
Script: https://github.com/nbyavuz/postgres-code-coverage/blob/main/code_coverage.sh
Live Report: https://nbyavuz.github.io/postgres-code-coverageWhether you're contributing to Postgres or just curious about test coverage trends, this is worth a look. Kudos to the author for making this public and maintainable!
If you have thoughts or suggestions, I’m sure they’d welcome feedback.
-
Seen this during my morning run.
made me think of generated unit tests... for generated code.
I came across this recently in a codebase, all in the noble pursuit of "code coverage."
#CodeThoughts #GeneratedTests #CodeCoverage #DeveloperLife #CodingInsights #SoftwareEngineering #ProgrammingHumor #iosdev -
Seen this during my morning run.
made me think of generated unit tests... for generated code.
I came across this recently in a codebase, all in the noble pursuit of "code coverage."
#CodeThoughts #GeneratedTests #CodeCoverage #DeveloperLife #CodingInsights #SoftwareEngineering #ProgrammingHumor #iosdev -
How can you use code coverage and mutation testing to add tests to legacy code? At @mendercon last year, I demonstrated this powerful technique step by step on the Gilded Rose kata, which is hosted by @emilybache on her GitHub account: https://github.com/emilybache/GildedRose-Refactoring-Kata
You can watch the talk here: https://www.youtube.com/watch?v=0qna5cuzDI0
#CSudberyRecordings #CodeCoverage #MutationTesting #GildedRose #Refactoring #UnitTests
-
How can you use code coverage and mutation testing to add tests to legacy code? At @mendercon last year, I demonstrated this powerful technique step by step on the Gilded Rose kata, which is hosted by @emilybache on her GitHub account: https://github.com/emilybache/GildedRose-Refactoring-Kata
You can watch the talk here: https://www.youtube.com/watch?v=0qna5cuzDI0
#CSudberyRecordings #CodeCoverage #MutationTesting #GildedRose #Refactoring #UnitTests
-
How can you use code coverage and mutation testing to add tests to legacy code? At @mendercon last year, I demonstrated this powerful technique step by step on the Gilded Rose kata, which is hosted by @emilybache on her GitHub account: https://github.com/emilybache/GildedRose-Refactoring-Kata
You can watch the talk here: https://www.youtube.com/watch?v=0qna5cuzDI0
#CSudberyRecordings #CodeCoverage #MutationTesting #GildedRose #Refactoring #UnitTests
-
How can you use code coverage and mutation testing to add tests to legacy code? At @mendercon last year, I demonstrated this powerful technique step by step on the Gilded Rose kata, which is hosted by @emilybache on her GitHub account: https://github.com/emilybache/GildedRose-Refactoring-Kata
You can watch the talk here: https://www.youtube.com/watch?v=0qna5cuzDI0
#CSudberyRecordings #CodeCoverage #MutationTesting #GildedRose #Refactoring #UnitTests
-
After starting and stopping a half-dozen times over the last few months, I finally sat down last night and spent ~3hr writing my thoughts on #CodeCoverage.
TL;DR: It's not without merit, but it is not the metric that many people make it out to be.
-
After starting and stopping a half-dozen times over the last few months, I finally sat down last night and spent ~3hr writing my thoughts on #CodeCoverage.
TL;DR: It's not without merit, but it is not the metric that many people make it out to be.
-
After starting and stopping a half-dozen times over the last few months, I finally sat down last night and spent ~3hr writing my thoughts on #CodeCoverage.
TL;DR: It's not without merit, but it is not the metric that many people make it out to be.
-
After starting and stopping a half-dozen times over the last few months, I finally sat down last night and spent ~3hr writing my thoughts on #CodeCoverage.
TL;DR: It's not without merit, but it is not the metric that many people make it out to be.
-
- "My library has 100% code coverage!"
- "How so?"
- "Because I test thoroughly"* opens editor *
* CTRL+F *
* @phpstan-ignore-line *
* Found 587 occurrences *
#Programming #PHP #PHPStan #Larastan #Laravel #Symfony #CodeCoverage #Coding #Code #SoftwareDevelopment #Software #WebDevelopment #WebDev
-
- "My library has 100% code coverage!"
- "How so?"
- "Because I test thoroughly"* opens editor *
* CTRL+F *
* @phpstan-ignore-line *
* Found 587 occurrences *
#Programming #PHP #PHPStan #Larastan #Laravel #Symfony #CodeCoverage #Coding #Code #SoftwareDevelopment #Software #WebDevelopment #WebDev
-
- "My library has 100% code coverage!"
- "How so?"
- "Because I test thoroughly"* opens editor *
* CTRL+F *
* @phpstan-ignore-line *
* Found 587 occurrences *
#Programming #PHP #PHPStan #Larastan #Laravel #Symfony #CodeCoverage #Coding #Code #SoftwareDevelopment #Software #WebDevelopment #WebDev
-
- "My library has 100% code coverage!"
- "How so?"
- "Because I test thoroughly"* opens editor *
* CTRL+F *
* @phpstan-ignore-line *
* Found 587 occurrences *
#Programming #PHP #PHPStan #Larastan #Laravel #Symfony #CodeCoverage #Coding #Code #SoftwareDevelopment #Software #WebDevelopment #WebDev
-
🔥 New TIL: Fixing Coverage for Django’s manage.py test --parallel
Running Django tests in parallel but coverage reports are inaccurate? Parallel test execution can mess up coverage data, but here’s how to fix it properly!
Read more 👉 https://til.sanyamkhurana.com/#/topics/django/fixing-coverage-for-djangos-managepy-test-parallel
-
🔥 New TIL: Fixing Coverage for Django’s manage.py test --parallel
Running Django tests in parallel but coverage reports are inaccurate? Parallel test execution can mess up coverage data, but here’s how to fix it properly!
Read more 👉 https://til.sanyamkhurana.com/#/topics/django/fixing-coverage-for-djangos-managepy-test-parallel
-
🔥 New TIL: Fixing Coverage for Django’s manage.py test --parallel
Running Django tests in parallel but coverage reports are inaccurate? Parallel test execution can mess up coverage data, but here’s how to fix it properly!
Read more 👉 https://til.sanyamkhurana.com/#/topics/django/fixing-coverage-for-djangos-managepy-test-parallel
-
"Will you write component tests with me?" 💍
Forget "Will you marry me?" as this is the real question of commitment. A perfect mix of unit and E2E tests, proving microservices true behaviour. Because nothing says "forever" like solid test coverage. 🛠️❤️https://martinfowler.com/articles/microservice-testing/#conclusion-summary
#CodingLove #TestingIsCaring #Microservices #ComponentTesting #UnitTests #E2ETests #DevHumor #TechRomance #CodeCoverage #QA #DevLife #coding #developer -
"Will you write component tests with me?" 💍
Forget "Will you marry me?" as this is the real question of commitment. A perfect mix of unit and E2E tests, proving microservices true behaviour. Because nothing says "forever" like solid test coverage. 🛠️❤️https://martinfowler.com/articles/microservice-testing/#conclusion-summary
#CodingLove #TestingIsCaring #Microservices #ComponentTesting #UnitTests #E2ETests #DevHumor #TechRomance #CodeCoverage #QA #DevLife #coding #developer -
"Will you write component tests with me?" 💍
Forget "Will you marry me?" as this is the real question of commitment. A perfect mix of unit and E2E tests, proving microservices true behaviour. Because nothing says "forever" like solid test coverage. 🛠️❤️https://martinfowler.com/articles/microservice-testing/#conclusion-summary
#CodingLove #TestingIsCaring #Microservices #ComponentTesting #UnitTests #E2ETests #DevHumor #TechRomance #CodeCoverage #QA #DevLife #coding #developer -
"Will you write component tests with me?" 💍
Forget "Will you marry me?" as this is the real question of commitment. A perfect mix of unit and E2E tests, proving microservices true behaviour. Because nothing says "forever" like solid test coverage. 🛠️❤️https://martinfowler.com/articles/microservice-testing/#conclusion-summary
#CodingLove #TestingIsCaring #Microservices #ComponentTesting #UnitTests #E2ETests #DevHumor #TechRomance #CodeCoverage #QA #DevLife #coding #developer -
🎥 Das dritte Video der BaselOne 2024-Serie ist online! 🎉
Wir wünschen euch allen ein gutes 2025 und hoffen, ihr seid gut gestartet! 🌟
In „Code Coverage Myth Busters“ zeigen Marharyta & Evgeny (Sonar), wie Code Coverage Qualität & Produktivität steigern kann – wenn es richtig eingesetzt wird.
🚀 Ein Muss für Java-Entwickler!
📺 Jetzt reinschauen: https://youtu.be/e7xWqkhLH8s
📅 Save the Date: BaselOne 2025 – 15. & 16. Oktober in der Markthalle Basel!