Urgent.News

What's breaking now, across thousands of outlets.

Tech

Do your tests really catch bugs? / Seus testes pegam erro de verdade?

I measured this together with Claude, ran research and tests, and built a garden about whether tests really catch bugs. The idea is simple: a test can pass and still be weak. To find out how weak, I broke the code on purpose and counted how many bugs the tests let through. Then I did the same for each step of my AI workflow, from the spec (the text that describes what the code should do) to the…

I measured this alongside Claude, conducting research and tests to create a digital garden exploring whether tests truly catch bugs. The concept is straightforward: a test may pass yet remain inadequate. To determine the extent of this inadequacy, I deliberately introduced flaws into the code and counted the number of bugs that managed to slip through the tests.

Subsequently, I replicated this process for each stage of my AI workflow, from the specification outlining the desired functionality to the final commit. In the digital garden, each stage is assigned a unique number, and notes detailing ideas that did not prove fruitful are also included. The garden also features a note addressing uncertainties, given the study's limited scope, its origin from a few projects, and the absence of external verification.

Additionally, a step-by-step guide is provided for replicating the measurement in your own project. A digital garden is an interconnected collection of notes maintained by the author over time, accommodating unfinished notes and displaying them with a badge indicating the level of provenance for each. To view the digital garden, visit Digital-Garden.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Design accessible form success states: status, navigation, Undo, and confirmation

Successful submission is a distinct UI state A completed form needs to answer two questions: did the action finish, and can the user recover if it was accidental?

  • Provide confirmation of successful action and undo option for reversible tasks
  • Use distinct announcement channels based on page transition
  • Focus status message on what was accomplished, not validation output

More from Saturday 14 November →