https://devopstoolkit.live/development/ai-testing-is-lying-to-you-and-you-cant-tell/index.htmlThere are three things that go into testing anything you build, and it doesn’t much matter what that is. An app, a cluster, a delivery pipeline, a pile of Terraform. You write them. You maintain them, because the thing underneath them keeps changing. And when the suite goes red on a Tuesday, you diagnose them, sorting the reds that mean something from the ones that are just flaky. Those are the worst kind, because a flaky red is how you learn to stop trusting reds at all. All three of those can be handed to an agent now. That sounds like every other job being automated right now, and mostly it is. But this one has a property nothing else in your pipeline has. When an agent writes your code badly, something catches it. That is what the tests are for. When an agent writes your tests badly, nothing catches it, because there is nothing underneath. A bad test doesn’t fail. It passes. And now you’re sure about something that isn’t true. You call all of this testing. So does everybody, and it’s a fair mistake, because the word is baked into every part of the work. You write a test. You run the test suite. You measure test coverage. You call the whole practice test automation. The word comes free, so nobody stops to ask whether it fits. It doesn’t. And the part of this that you assume will always need a person is going the same way as the rest of it. I’ll come back to both of those. For now, keep thinking you’re testing.Hugoen-us