Title: I&#x27;ve been a developer working for large corporations for the past 4 who are more concerned with &quot;fast&quot; delivery than &quot;correct&quot; delivery. As a result of that, the concept of Unit Testing is somewhat foreign in the environment (I think we have somewhere around 40% test coverage, our unit test suite takes ~40 minutes to run on a dev machine, and new unit tests rarely get written). Unit tests aren&#x27;t &quot;valuable&quot; to the customer, so they are pushed out in favor of &quot;value&quot; code (features) and the reliance on manual QA testers to catch defects (which doesn&#x27;t happen).<p>Imagine you were hired as a consultant to come in here and fix our process. How would you sell TDD to the bosses&#x2F;managers who only see it as extra work for the same value? I&#x27;ll admit I&#x27;m a little fuzzy on the benefits as well. I&#x27;m slightly ashamed to admit that even on my side projects I&#x27;m like &quot;I&#x27;m totally gonna do TDD you guys!&quot; but that rapidly falls by the wayside.
Upvote: