It’s because people don’t know how to write tests. All of the “don’t do N select queries in a for loop” comments made in PRs are completely ignored in tests. E

It’s because people don’t know how to write tests. All of the “don’t do N select queries in a for loop” comments made in PRs are completely ignored in tests. Each test can output many db queries. And then you create multiple cases. People don’t even know how to write code that just deals with N things at a time. I am confident that tests run slowly because the code that is tested completely sucks and is not written for batch mode. Ignoring batch mode, tests are most of the time written in a a way where test cases are run sequentially. Yet attempts to run them concurrently result in flaky tests, because the way you write them and the way you design interfaces does not allow concurrent execution at all. Another comment, code done by the best AI model still sucks. Anything simple, like a music player with a library of 10000 songs is something it can’t do. First attempt will be horrible. No understanding of concurrent metadata parsing, lists showing 10000 songs at once in UI being slow etc. So AI is just another excuse for people writing horrible code and horrible tests. If it’s so smart , try to speed up your CI with it.