> tests are there to make sure code works, not for tests' sake. It works is awfully imprecise. Are you talking about perfect code? Some specific use-case? Some

> tests are there to make sure code works, not for tests' sake. It works is awfully imprecise. Are you talking about perfect code? Some specific use-case? Some project-specific level of quality? Ordinary (non-fuzzing) tests are generally there to help protect against regressions when changing existing functionality, or to offer baseline quality assurance for new functionality. They can also be helpful in, say, determining whether the code behaves as expected when using a different compiler. They aren't normally how you discover a long-standing bug. There's always more to software quality than just testing.