Comment by shykes
5 hours ago
Think of it as a layered problem. If the bottom layer (CI) cannot keep up with the output of agents, then solving problems at a higher layer - like user experience checks - will be exponentially slower and less reliable. Kind of like how optimizing tight inner loops makes your whole program faster.
It's true because it usually makes no sense to QA test a build where the test suite has not yet passed.
Uh, no. If stage X is the bottleneck, it's immaterial how much you speed up stage Y.
You're assuming QA reviews won't be fully automated, and triggered from a CI pipeline.
QA is not automatable. QA is about finding the things that you didn't think of and so didn't write a test for it. That many people think qa is not important shows in the bad software we have.
We can assume lots of things, but at some point the rubber must hit the road.
What exactly are you using to back up this claim?
> QA reviews [...] fully automated