Testing is the last leg in your journey to Rails development greatness. With tests, you know you can build apps faster, confidently add new features without breaking old ones, and debug much more efficiently. You might even know how to test with all the great tools and frameworks out there. Your problem is that you just don't know what to test.
Veteran developers will tell you this is how to test with TDD:
- Write a test that fails.
- Write fast, isolated code that isn't allowed out past 10pm.
- Watch that test pass.
- Refactor your code so it’s beautiful and brings all the boys to your yard.
Here's your problem: Step one. Write a test. There's a lot that goes on first step than meets the eye. If you've been struggling to understand testing in Rails, look no further, because in this book, you'll learn:
- The missing steps in the testing process
- That it's ok not to test first
- When you should test and when you should tinker
- How to build and test a new feature
- What you need (and don't need) to test
Hi. I'm Eric.
I've been building things with Rails for three years, and trying to figure out how to test for almost as long. By day, I'm a Rails product consultant, and by night, well I guess I'm still a Rails product consultant, only it's darker outside. You should follow me @genericsteele.