I know some people don't test at all and some have their users test in Production. No judgement.Assuming your teams test, Dev->Staging->Prod, local dev or ephemeral env's. What do you think the critical path is to help you go faster other than increasing raw Eng bandwidth:- Write code more efficiently? - CI/CD pipelines - build/deploy faster? - Test earlier, test faster, test better?
One of the core premises of what we've been trying to do with our product (Testkube) is to decouple Testing from CI/CD's. Those were never built with testing in mind, let alone scaling to 100's or 1000's of efficient executions. We have a light weight open-source agent, which lives inside a K8s cluster, tests are stored as CRD's cloned from your GIT, executed as K8's jobs. Create whatever heuristics or parallelization necessary, leverage the power of K8s to dynamically scale compute resources as needed, trigger executions by whatever means (GitHub Actions, K8s' events, schedule, etc.), do it on your existing infra.
Admittedly, we don't solve the test creation problem. If there are new tools out there which could automagically generate tests along with code, please share.