How I Write Tests
Excellent article and it&#x27;s perfect timing for me!<p>In the past while contracting I was usually asked to include in my proposals estimates for tests.<p>The tests failed to be useful, simply because they were written <i>after</i> the feature was actually implemented! We knew better, of course, but this was done in order to quickly get builds a client could look at.<p>Then when clients wanted to add&#x2F;change features guess what got cut to make up for the time? Thats right, the tests!<p>So the tests were always secondary, and the projects tended to suffer as a result.<p>Recurring &quot;fixed bugs&quot; cost more than just working hours to fix.
In the eyes of a client or customer, they are so much worse than a shiny new bug.
Tests can help catch recurring bugs <i>before</i> a client&#x2F;customer does - and save you not only time,
but from losing your customers confidence.<p>Now, I&#x27;m building my own app and I&#x27;m using a diciplined TDD approach. 
I didn&#x27;t start my project this way as It seemed overkill when it was just me. But I saw early on that to not practice TDD even solo was madness.
It <i>is</i> taking longer, but my actual progress is consistent, and I&#x27;m already far more confident about the stability of the app.