Permalink
Browse files

added the page "automate everything"

  • Loading branch information...
1 parent a51b614 commit 531beb30da54ec124d29b8b547108a34fb00b7cb @joelmccracken committed Mar 17, 2011
Showing with 68 additions and 0 deletions.
  1. +11 −0 _posts/2011-03-17-posted-automate-everything.markdown
  2. +54 −0 content/automate-everything.markdown
  3. +3 −0 index.html
@@ -0,0 +1,11 @@
+---
+
+layout: post
+title: Posted "Automate Everything"
+---
+
+Test Driven Development has bothered me, as it seems to be part of a
+greater idea. I think I have figured out what it is.
+
+
+[Automate Everything](/content/automate-everything.html)
@@ -0,0 +1,54 @@
+---
+
+layout: page
+title: Automate Everything
+---
+
+Ever since I started to practice Test Driven Development, it has bothered me. While
+it is a really great and
+process, I always felt like it was a shadow of another idea. There are
+many things that are really similar to TDD, but aren't part of the
+testing process.
+
+For example, I always noticed that testing out the way your function
+behaves in an interactive shell is really similar to writing a
+test. Indeed, they seem to be almost the same
+thing<sup><a href="#python-for-example">1</a></sup>. Why are they so
+similar?
+
+Or, whenever I am learning a new library, I play around with
+it, trying to figure out how it works, and specifically how it should
+be useful for the purposes of my project. Here's the thing -- if I
+were to change these shell sessions into test suites, it
+*would provide documentation about that library that is suited to my particular
+situation*.
+However, *writing tests for external code is considered wrong*. So,
+while I see the usefulness as documentation, it is also wrong. Highly
+useful, and wrong. This bothers
+me. If doing something like that is beneficial, why shouln't I do
+it?
+
+All of this made testing seem like a small piece of a greater,
+possibly more important practice, and for the first eight months or so
+of my practicing TDD, they bothered me. Until one day, inspiration
+struck.[Test Driven Development isn't *really* about *testing*, it is about
+*automation*](/content/automatic-test-driven-development.html).
+We can automate ourselves, and this
+can bring tremendous benefit -- benefit on the level of what test
+driven development brings.
+
+Suddenly, these strange issues seemed to melt away. That
+library-documenting code that I was talking about? It isn't
+testing. But, it is still something that can be really useful if
+*automated*.
+
+So, I'm trying it out. It seems like a hunch worth testing. I am
+making a strong effort do figure out what
+areas of my life could benefit from automation, and I'm figuring out
+what the best way to do it is. I hope to post the results here.
+
+<span class="footnotes">
+1. <a id="python-for-example"></a> Check out
+[Python's doctest library](http://docs.python.org/library/doctest.html)
+for an interesting look at this idea.
+</span>
View
@@ -12,6 +12,9 @@
<h1>content</h1>
<ul class="posts">
+ <li>
+ <a href="/content/automate-everything.html">Automate Everything</a>
+ </li>
<li>
<a href="/content/automatic-test-driven-development.html">Automatic
Test Driven Development</a>

0 comments on commit 531beb3

Please sign in to comment.