(public).sospep.subjects ~ view article ~ Giving-up-on-test-first-development

<h1 style="text-align: center;">Giving up on test-first development</h1>
<h2>[WHAT]</h2>
<ol>
<li>] by Ian Sommerville @ iansommerville.com - &nbsp;</li>
</ol>
<h2>[WHY]</h2>
<ol>
<li>]&nbsp;</li>
</ol>
<h2>[WHERE]</h2>
<ol>
<li><strong>] READ THE FULL ARTICLE</strong></li>
<ol>
<li>]&nbsp;<a href="http://iansommerville.com/systems-software-and-technology/giving-up-on-test-first-development/" target="_blank">http://iansommerville.com/systems-software-and-technology/giving-up-on-test-first-development/</a></li>
</ol></ol>
<h2>[WHEN]</h2>
<ol>
<li>] 2016-03-dd</li>
</ol>
<h2>[EXAMPLE]</h2>
<ol>
<li>You write a program to pass the test, extend the test or add further tests and then extend the functionality of the program to pass these tests.</li>
<li>The tests serve as the program specification so you have a detailed but abstract description of what the program should do.</li>
<li>As I started implementing a GUI, the tests got harder to write and I didn't think that the time spent on writing these tests was worthwhile.</li>
<li>I became less rigid in my approach, so that I didn't have automated tests for everything and sometimes implemented things before writing tests.</li>
<li>I'm giving up because I think it encourages conservatism in programming, it encourages you to make design decisions that can be tested rather than the right decisions for the program users, it makes you focus on detail rather than structure and it doesn't work very well for a major class of program problems - those caused by unexpected data.</li>
<li>The best design is one that's hard to test so you are more reluctant to take this approach because you know that you'll spend a lot more time designing and writing tests The most serious problem for me is that it encourages a focus on sorting out detail to pass tests rather than looking at the program as a whole.</li>
<li>I'll continue to test automatically wherever it makes sense to do so, but I won't spend ridiculous amounts of time writing tests when I can read the code and clearly understand what it does.</li>
</ol>
<h2>[HOW-TO]</h2>
<ol>
<li>]</li>
</ol>
<h2>[REFERENCE]</h2>
<ol>
<li>] SRC = HN, <a href="https://news.ycombinator.com/item?id=11310711" target="_blank">comments</a></li>
</ol>
<h1 style="text-align: center;">&nbsp;</h1>

~ view article ~ Chapter] index FROM [ Book] strategy-software-developer IN [ libraries] technology-developer-software