A lot of things are always easy to mention and then forgotten; such as developing unit tests and automated testing.
I think this is related to the enterprise culture and the process level of the development and testing team. If we have been "agile" in our work and have gone away with the demand analysis and detailed design time, we cannot bear the reduction in efficiency brought about by the early stages of unit testing, it is also impossible to maintain the existing unit test script. Similarly, if neither of the test groups can participate in the demand discussion at the very beginning, few functional modules cover the test cases, and even are in the initial stage of "smoke, it is certainly far from the testing automation stage.
What we need to do is not to emphasize the importance of testing after each problem arises, nor to imagine or envy the convenience brought by other people's automated testing and the reduction of testing costs (this is impossible ), instead, we can know where the next step is.