To my belief, over-complicated testing projects that get abandoned by teams are a much more damaging reality that is already deep within the industry.

One example might be a legacy code with a class that expects 6 different providers in its constructor that need to be initialized with their child dependencies. Also, this class spans 2% of the application code. My advice: don’t insist to test this, START with the easier part to get some reasonable confidence. Finally, if there is time left — handle this. In 99% of the cases, the team won’t have time, but at least they covered most of app