In my previous post on understanding TDD I discussed how to analyze existing code for creating unit tests. This was somewhat of “reverse TDD”, the idea being to look for what to needs to be tested- the relationship between what one class expects and what another class actually does. Unfortunately I stopped short of actually implementing those tests- which is the subject of this post.
Good Posts from the Net
- Rails Reminder: DATE_FORMATS jason
- CSS3 Please! Instant results… Thank You Dion Almaer
- Uncovering jQuery’s Hidden Features James Padolsey
- 12 Steps to MooTools Mastery Jacob Thornton
- 6 Places to Find Superb, High Quality Mac Icons David Appleyard
- 3 Fantastic Uses of the Photoshop High Pass Filter Andrew Gibson
- 55 Colorful Web Designs to Inspire You gmuller
- Boxed Ice: Notes from a Production Deployment John Nunemaker
- Using acts_as_archive instead of soft delete Luke Francl
- Comprehensive One Page MongoDB Overview John Nunemaker