Score Two for Unit Tests

I just got back from my long weekend, and I had trouble remembering exactly what it was I was supposed to be up to. So, I ran my unit tests, and there it was — my failing unit test reminder of work to be done!

Even better, I thought I had implemented it, ran the test, and discovered that I had forgotten to persist the change to the database. The unit test caught that, so now I’ve really got confidence the code works.

Score two for unit testing.

Related posts:

  1. My Great Secret to Writing Unit Tests
  2. The Joy of Unit Tests
  3. A Tricky Trap With Unit Test Mocks in Dynamic Languages
  4. Score One for Obama
  5. Ruby on Rails: Fixtures Gotcha
This entry was posted in To Be Categorized and tagged . Bookmark the permalink. Post a comment or leave a trackback: Trackback URL.
  • Categories