🚨Most teams know their #CodeCoverage numbers, but can they tell which features are actually tested? Join See how #FeatureCoverage helps teams track testing across frameworks & where AI accelerated the process. 🔒 testguild.com/automation-gui… #AutomationGuild 2026 exclusive.

Use Visual Studio Pro's built-in code coverage tools to identify untested code paths. Run tests with coverage enabled, review the coverage report, and focus on improving tests for low-coverage areas to boost code quality and reliability. #CodeCoverage #VSPro @visualstudio

📊 Most teams know their #CodeCoverage numbers. But can they tell which features are actually tested? Join Sachin to learn how #FeatureCoverage provides better visibility across Cucumber, TestNG & Playwright. Exclusive to #AutomationGuild 2025 members. testguild.com/automation-gui… 🚀

Data informs testing. It doesn't replace judgement. 🧠 Day 7 of My QA Journey 💯 #CodeCoverage #QA #TestAutomation #ContinuousIntegration #CI #DevOps #SoftwareTesting #QAEngineer #TestStrategy #SoftwareTesting #LearningInPublic

Looping Cursor Headless CLI to auto-fix tests raise coverage is now part of my tools. Ralph loop enabled! #CursorIDE #SoftwareEngineering #Testing #CodeCoverage #Automation #DevTools

🎄🎉Happy Holidays everyone, I wish health to every single one of you🎉🎄 Jest in 2025: what it is, why it’s “delightful,” and how to use it well. Jest is a JavaScript testing framework that bundles a test runner, assertions, mocking, snapshots, and coverage into one tool, aiming for a simple setup and a fast feedback loop for both beginners and experienced teams. @jestjs_ 🔗Tap below to dive deep into it👇 bytebrief.vercel.app/blog/je… #Jest #JavaScriptTesting #UnitTesting #TypeScript #TestRunner #Mocking #SnapshotTesting #CodeCoverage #FrontendTesting #WebDevelopment #DevTools #TestingFramework

(4/n) after the build happens, different tests are run against the compiled binary. for eg. unit/integration/e2e tests. there are codecoverage checks too that checks for the coverage of code by tests.

For a few weeks I am working on improvements for #phpunit #codecoverage features. Just relased a blog post detailling the approach and all the ideas and results including deep links into all the relevant pull requests. staabm.github.io/2025/11/26/…

Microsoft continues to patch bugs found through my Office fuzzing project. Today they have patched: - Microsoft Word Remote Code Execution Vulnerability (CVE-2025-59221) msrc.microsoft.com/update-gu… - Microsoft Word Remote Code Execution Vulnerability (CVE-2025-59222) msrc.microsoft.com/update-gu… These two bugs are in a new attack vector specific to Microsoft Word. It took me a really significant amount of time and energy to help MSRC reproduce the issues (see the timeline for CVE-2025-59221/97766 linkedin.com/posts/haifeili_…). Despite all the HUGE effort, MSRC rated the quality as "low" (which I still personally disagree with:P). Let me take a break and review for my year-long journey in Office bug hunting since I started this project (which I wanted to do for a long time) last October. I’m happy to report that I’ve reported approximately 28 Office bugs during this journey. Most of them have been patched and were in Microsoft Word (see the list below), few were duplicated or non-exploitable though, and there are still 7 or 8 bugs waiting to be confirmed and patched by Microsoft. October 2025: - Word RCE, CVE-2025-59221 - Word RCE, CVE-2025-59222 August 2025: - Word RCE, CVE-2025-53738 - Word RCE, CVE-2025-53784 July 2025: - Word RCE, CVE-2025-49699 - Word RCE, CVE-2025-49700 June 2025: - Word RCE/heap-overflow, CVE-2025-32717 - Word RCE, CVE-2025-47170 - Word RCE, CVE-2025-47957 May 2025: - Outlook RCE, CVE-2025-32705 - PowerPoint RCE, CVE-2025-29978 April 2025: - Word RCE, CVE-2025-29820 March 2025: - Word RCE, CVE-2025-26629 - Word RCE, CVE-2025-24077 - Word RCE, CVE-2025-24078 - Word RCE, CVE-2025-24079 - Word RCE, CVE-2025-24080 February 2025: - Word RCE, CVE-2025-21392 - Word RCE, CVE-2025-21397 For me, this proves that my systematic, code-coverage-based bug hunting methodology is effective and powerful. By maximizing code coverage in the target application, even with mature software like Microsoft Office, you can still find a lot of bugs. For Microsoft and the general public (Office users), I believe together we've made Office much safer by patching various bugs across different attack vectors. Thank you to all the Microsoft folks who have worked with me. I will probably continue this journey, as I know I’ve only scratched the surface of this vast challenge. My fuzzing system still generates new code coverage (samples) every day, and there are many "adjustments" to the fuzzer to target different attack vectors and during the bug analyzing process, I continued to learn about new attack vectors. There's still a lot of work to do if I receive support. But for now, let me take some vacations first. :) #PatchTuesday #VulnerabilityResearch #OfficeSecurity #fuzzing #codecoverage

Use Visual Studio Pro's built-in code coverage tools to identify untested code paths. Run tests with coverage enabled, then review the coverage report to improve test completeness and boost code quality efficiently. #CodeCoverage #VisualStudioPro @visualstudio

Differential code coverage for #PostgreSQL—automated daily! Track what’s tested between HEAD and REL_18_STABLE. Live report:nbyavuz.github.io/postgres-c… Script:github.com/nbyavuz/postgres-… Kudos @nbyavuz #CodeCoverage #OpenSource

Today I worked on phpunit/php-code-coverage to improve #phpunit performance when generating #codecoverage reports. the just pushed release improves my example use case by ~33%. Consider sponsoring my open source work in case you love such fixes :-)

#AgenticAI tools 🤖 are offloading routine tasks but they are also introducing non-human #coding behaviors. 🔍 Learn how #codecoverage tools is the solution: bit.ly/4jYNJYs Catch #AI logic bugs & errors 👾 that traditional testing might miss!

Supercharge your testing with AI! @Parasoft now integrates #agenticAI to elevate API testing and boost code coverage analysis. See how this smart integration transforms your dev pipeline: talkdev.com/quick-bytes/para… #APITesting #CodeCoverage #AgenticAI #Parasoft #DevOps

DevOps security Nana - CodeCoverage is very important and lots of companies are missing rigjt policies

🔍 Code Coverage in Java – What's your team's target? ✅ 70-80% ✅ 80-90% ✅ 90% Learn more here 👉 techoral.com/java/java-code-… #Java #CodeCoverage #JUnit #SoftwareTesting #JaCoCo #SonarQube #DevOps #TestAutomation #CodeQuality #UnitTesting #SoftwareEngineering #Techoral

🔍 Code Coverage in Java – What's your team's target? ✅ 70-80% ✅ 80-90% ✅ 90% Learn more here 👉 techoral.com/java/java-code-… #Java #CodeCoverage #JUnit #SoftwareTesting #JaCoCo #SonarQube #DevOps #TestAutomation #CodeQuality #UnitTesting #SoftwareEngineering #Techoral

Last chance to register for our Code Coverage webinar tomorrow to learn how to… 🔎 Harness unit test and #codecoverage metrics 🛠️ Implement coverage analysis with Sonar 🚀 Improve code reliability and developer productivity Save your spot: bit.ly/437FMeS

Deploy code with confidence. 💯 Learn to master code coverage and supercharge your development workflow in our webinar on March 26th. 📆 Details here: 👉 bit.ly/437FMeS #CodeQuality #CodeSecurity #Developers #CodeCoverage #TechWebinar