Merging modern software development with electrons and metal
Random header image... Refresh for more!

The purpose of Test Driven Development

I was going through an old stack of JDJ‘s (Java Developer Journals), and saw an interesting commentary on Test Drive Development (TDD). The author said its purpose was to help you write the minimal amount of code necessary to meet the current requirements, and that having a test suite available was a nice side affect. His TDD development sequence is:

  1. Write tests that show your requirements, based on the perfect client interface
  2. Write just enough code to compile successfully
  3. Write just enough so that all the tests pass
  4. Refactor

Now apply this idea to the world of factory automation software. Hmm, could be interesting, but it wouldn’t work with PLC’s (rllUnit anyone? I don’t want to even imagine porting xUnit to IEC61131.)



There are no comments yet...

Kick things off by filling out the form below.

Leave a Comment