Colin Law wrote: > I suggest starting with a very simple test and get that working first. > Use the debugger to find out what is going wrong if you cannot get it to > behave correctly.
Further, if you cannot _briefly_ get the test working, comment it out and write a simpler test, maybe on another feature. Test the models first, for example. The goal here is breadth-first, not depth first. The more tests you write, the more "muscle memory" you develop, and the easier new tests get. You might come back to this validation problem, for example, and just knock it out easily... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
