How to convince team other parts of software development are important?

Sometimes, when I present a part of the software development process to certain people, say the supervisor or the manager that they don't have experience say

1. Automated unit tests and integration tests vs. their manual functional testing.
2. Using code generators, and scripts for repetitive tasks.

I sometimes met with resistance. Some of the reasons are the following:

1. They say that that's the way we do things here. Our system works and there is no need to add in our process.
2. They are busy being busy. They say is their job is to get us projects and our job is to deliver it to them to their satisfaction. They are satisfied when if it is a manual system, repetitive but on time.
3. They are very conservative about code generators. I gave them an estimate that it takes a significant time overhead for the first project to use this and time to train my teammates since this approach is relatively new to them. The overhead for the first project to them overshadows the benefit in the long run, but I explained the convenience it is to us developers, but they are always stuck to do things the old way.

What would be your strategy for this?

Wait for a problem to show up and then make your move.