In those situations, I'd run overnight mutation testing jobs that cover all the code, and during the day incremental mutation testing on code that's changed. And code that's changed would be refactored to turn its tests into "unit" tests.

I'm well aware of the testing pyramid. I'm just saying that if you have a testing diamond, or an upside-down pyramid, that doesn't necessarily rule out mutation testing these days.

What if all your tests are integration tests?

The first time, sure. But many mutation testing tools now support incremental testing - just the code that's changed.

Well, it beats actually innovating!

My first question would have been "What's the training cost?"

Because his business size suggests it's f**k all.

No moat.

Think of your automated regression tests as a police force. Wanna know how good they are catching burglars?

There's a simple way to check.

It's not settling. Phew.