I think it's important to note that it takes time and practice to get new techniques delivering speed and quality improvements.
You wont get it right first time. Each time you improve on what you had before until a lot of seemingly minor changes coalesce to become a huge transformation.
Lets suppose you start by getting production infrastructure dashboards on the walls where your developers work. It seems like a cosmetic change until the infrastructure guys explain the significance of the various measures. The next thing that happens is that the developers identify those measures that? their work influences. The infrastructure guys then have another instructional piece to explain how individual metrics may lead to false conclusions but specific combinations have particular significance. The developers then find ways to access the underlying metric data so they can automate stress tests etc.
Thinking of tests up front may improve the breadth of the tests from the outset but adding to tests later as a sadder, wiser developer will simply be the same destination by a longer, more painful route. At the end of it you will still have vastly more tests than you would ever run manually and executed Consistently.