{"id":242,"date":"2011-06-15T16:01:45","date_gmt":"2011-06-15T20:01:45","guid":{"rendered":"http:\/\/dashdrum.com\/blog\/?p=242"},"modified":"2011-06-15T16:01:45","modified_gmt":"2011-06-15T20:01:45","slug":"tdd-works-better-up-front","status":"publish","type":"post","link":"https:\/\/dashdrum.com\/blog\/2011\/06\/tdd-works-better-up-front\/","title":{"rendered":"TDD Works Better Up Front"},"content":{"rendered":"<p><a href=\"http:\/\/en.wikipedia.org\/wiki\/Test-driven_development\"><img loading=\"lazy\" decoding=\"async\" alt=\"\" src=\"http:\/\/upload.wikimedia.org\/wikipedia\/en\/thumb\/9\/9c\/Test-driven_development.PNG\/350px-Test-driven_development.PNG\" title=\"TDD Flowchart\" class=\"alignright\" width=\"350\" height=\"251\" align = \"right\" vspace=11 hspace=11 \/><\/a>For the Django app I deployed last month, I had started the process using a <a href=\"http:\/\/en.wikipedia.org\/wiki\/Test-driven_development\">Test Driven Development<\/a> (TDD) approach.  In a nutshell, it means that tests are written before a feature is coded.  This went well at the beginning, but as crunch time neared, the tests were thrown by the wayside and code was tossed in as needed.<\/p>\n<p>Now that I&#8217;m in this <a href=\"http:\/\/dashdrum.com\/blog\/2011\/05\/upgrading-django-1-0-to-1-3\/\">Django upgrade project<\/a>, I decided to go back and complete the tests before starting the upgrade work.  It is now three weeks later, and I still have much to do (working on my own time &#8211; not during work hours).  However, I&#8217;m really enjoying the satisfaction that passing a well written test can bring.<\/p>\n<p>My hope is that my next project will be more TDD compliant, as I am learning the skills now that I need to write quality tests quickly.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>For the Django app I deployed last month, I had started the process using a Test Driven Development (TDD) approach. In a nutshell, it means that tests are written before a feature is coded. This went well at the beginning, but as crunch time neared, the tests were thrown by the wayside and code was &hellip; <\/p>\n<p class=\"link-more\"><a href=\"https:\/\/dashdrum.com\/blog\/2011\/06\/tdd-works-better-up-front\/\" class=\"more-link\">Continue reading<span class=\"screen-reader-text\"> &#8220;TDD Works Better Up Front&#8221;<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[],"tags":[],"class_list":["post-242","post","type-post","status-publish","format-standard","hentry"],"_links":{"self":[{"href":"https:\/\/dashdrum.com\/blog\/wp-json\/wp\/v2\/posts\/242","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dashdrum.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/dashdrum.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/dashdrum.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/dashdrum.com\/blog\/wp-json\/wp\/v2\/comments?post=242"}],"version-history":[{"count":3,"href":"https:\/\/dashdrum.com\/blog\/wp-json\/wp\/v2\/posts\/242\/revisions"}],"predecessor-version":[{"id":245,"href":"https:\/\/dashdrum.com\/blog\/wp-json\/wp\/v2\/posts\/242\/revisions\/245"}],"wp:attachment":[{"href":"https:\/\/dashdrum.com\/blog\/wp-json\/wp\/v2\/media?parent=242"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dashdrum.com\/blog\/wp-json\/wp\/v2\/categories?post=242"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dashdrum.com\/blog\/wp-json\/wp\/v2\/tags?post=242"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}