Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

added the page "automate everything"

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

0 notes on commit 531beb3

Please sign in to comment.
Something went wrong with that request. Please try again.