This post originated from an RSS feed registered with Ruby Buzz
by Daniel Berger.
Original Post: Unit testing strategies
Feed Title: Testing 1,2,3...
Feed URL: http://djberg96.livejournal.com/data/rss
Feed Description: A blog on Ruby and other stuff.
Here's a few things I always try to remember to do when I'm writing tests:
1) Test against explicit nil. It's easy to get caught with your pants down when using chained methods. NullPointerException anyone?
2) Test against 0. Remember boys and girls, 0 is not false in Ruby.
3) Check for expected exceptions. You should generally have a smattering of assert_raises somewhere in your test suite. It's also a good way to fish out segfaults in C extensions on occasion.
Previous Topic
