It isn't learned because 99% of the time, it works fine and nothing bad happens.
We are very bad at avoiding these sorts of rare, catastrophic events.
That's why the most reliable way to instil this lesson is to instil it into our tools. Automate as much testing as possible, so that bypassing the tests becomes more work than running them.
I disagree, it's in part a people problem - more draconian test suites just make developers more inclined to cheat and they tend to write tests which are not valid or just get the tool passing...
It's more important to visually model and test than to enforce some arbitrary set of rules that don't apply universally - then you have at least the visual impetus of 'this is wrong' or 'I need to test this right'.
A lot of time is spent visually testing UIs and yet these same people struggle with testing the code that matters...
Until a manager is told about how hard the automation makes it to accomplish their goal...
You need buy-in to automation at a high enough level.
If a team manager at eg Google was complaining about how automation gets in the way and wanted to bypass it, they wouldn't last too long.
Managers who have been bitten still make this choice
That lesson will really never be learned. This happens on a daily basis all over the planet with people who have not been bitten - yet.