Previous articles

Summary Pull Request Coverage offers a clearer and more accurate way to measure the quality of code being introduced in a PR. Unlike global project coverage, which can hide newly introduced untested logic, PR...

Many API security failures aren’t caused by unknown vulnerabilities or sophisticated attacks. They stem from implicit assumptions, authorization rules and data-access...

As the ExpressoTS codebase grew, test coverage no longer reflected real confidence in the system. Using Early, an AI code generation agent that writes executable unit test...

‍

AI-assisted code generation ⓘ is no longer experimental—it’s rapidly becoming the standard across engineering teams. Code that once took days to write can now be produced in...

It would be ideal if software were developed without bugs. In reality, bugs are introduced every time new code is written, and this is getting 100× worse in the era of...

This is my second article in the journey of AI for testing following From AI Assistants to Collaborative Agents: The Future of Software Testing .

The CEOs of Shopify and Fiverr recently reminded us that AI is no longer optional - it's becoming the backbone of modern workflows. Yet, the term “AI” covers a wide range...

Most teams treat unit tests like a safety net but that net has holes. Hitting 100% test coverage looks impressive in CI dashboards, but it often hides the truth: you’re not testing the right things. Minor changes...

Production bugs wreck sprints—you lose time digging into logs and rushing fixes, and debugging in production risks stability and stalls meaningful progress.

Have you ever run a unit test that failed the first time but magically passed on a second try? Or spent forever debugging, only to discover the actual bug was in the test itself? These headaches are typical in...

Ever written a React unit test that passed today and failed tomorrow for no apparent reason? You’re not alone.