https://www.thinkulum.net/w/index.php?action=history&feed=atom&title=Software_Development%2FTest-First_Programming 2026-04-21T13:12:09Z Revision history for this page on the wiki MediaWiki 1.37.1 https://www.thinkulum.net/w/index.php?title=Software_Development/Test-First_Programming&diff=375&oldid=prev 2019-02-22T05:00:28Z

<p>Added the article.</p> <p><b>New page</b></p><div>* [https://martinfowler.com/bliki/TestDrivenDevelopment.html TestDrivenDevelopment - Martin Fowler]<br /> * [http://agiledata.org/essays/tdd.html Introduction to Test Driven Development (TDD) - Agile Data]<br /> * [https://www.facebook.com/notes/kent-beck/rip-tdd/750840194948847/ RIP TDD - Kent Beck - Facebook]<br /> <br /> To get myself into the habit of writing tests first, I'm including it as a subtask for each function I note in my task manager (I use [https://nirvanahq.com/ Nirvana], an app designed with [https://en.wikipedia.org/wiki/Getting_Things_Done GTD] in mind). I have a template for these subtasks, which I copy into the description of the tasks. At the moment the template looks like this:<br /> <br /> &lt;pre&gt;<br /> - Document<br /> - Test<br /> - Code<br /> - Commit<br /> &lt;/pre&gt;<br /> <br /> Really I'll move back and forth between documenting, testing, and coding, but I'll check them off when I've completed the first instance of each of those subtasks for that function.<br /> <br /> A practice I'm starting to explore that takes TDD a step further is behavior-driven development. It allows you to derive tests from documentation that's both human readable and executable.<br /> <br /> * [https://en.wikipedia.org/wiki/Behavior-driven_development Behavior-driven development - Wikipedia]<br /> * [https://github.com/cucumber/cucumber/wiki/Python Python - cucumber Wiki] - A short list of Cucumber alternatives for Python.<br /> <br /> [[Category:Programming]]<br /> [[Category:Essays]]<br /> [[Category:Developing]]</div>

Andy Culbertson