I don't see test coverage as a goal or even interesting. I use TDD exclusively to write the code, and never write code that isn't already exercised by a test, so the coverage takes care of itself. The whole notion of test coverage comes from a spaghetti-code-monolith world where nobody has any idea if anything at all is being tested. In that mess of a system, a test-coverage-detection tool can act as a wake-up call. No coverage? Wake up! When you approach writing the code more systematically—well defined components that have a single responsibility and focused API, for example—you don't need to worry about tools that make sense in a different environment entirely.

Source: x.com/allenholub/status/1848430375032217974