How I learned to test my Rails applications, Part 5: Request specs

What's that? Something about me working on a book about RSpec?

Keep it simple: If you don’t get request specs right away, don’t worry about it. They require some additional setup and thinking to not just work, but actually test what you need to test. Don’t stop testing your models and controllers, though—building skills at that level will help you grasp more complicated specs sooner rather than later. Make time for testing: Yes, tests are extra code for you to maintain; that extra care takes time. Plan accordingly, as a feature you may have been able to complete in an hour or two before might take a whole day now. This especially applies when you’re getting started with testing. However, in the long run you’ll recover that time by working from a more trustworthy code base. Don’t revert to old habits! It’s easy to get stuck on a failing test that shouldn’t be failing. If you can’t get a test to pass, make a note to come back to it—and ...

Full article: http://everydayrails.com/2012/04/24/testing-series-rspec-...