Too Many Paths? Polymorphism to the Rescue!Ĭhapter 6: Contributing to Laravel Using TDDĬhapter 13: Test-Driving Artisan Commands Exercise I'm about 1/2 through #LaravelTestingDecoded and it's already probably one of the most valuable programming bookings I've read!Ĥ Ways to Spot a Class With Too Many ResponsibilitiesĤ. Getting those "Ahas" while reading your book. I'm sure you hear it a lot, but I pay my bills and make my living off what I learned from you. Polymorphism in the usually cliche calculator example? Mocks without my brain bleeding? Happy Gilmore references? Screw O'Reilly, I'll buy everything you write. Not only does it teach testing, but the examples themselves drill best practices into your psyche. I thought testing was lame, but now I don't think I'll be able to write an app without thinking "is this testable?" If you're on the fence, buy this book. This is one of the best programming books I've read in quite awhile. It’s worth at least twice the money I paid for it. Just finished reading Laravel Testing Decoded. This book is as much an introduction to TDD as it is a deep analysis of the Laravel way of testing applications. While the principles of testing (and TDD) are language-agnostic, when it comes to execution, there are a variety of tools and techniques at your finger tips. Trust me: as soon as you bring the phrase " how could I test this" to the forefront of every new piece of code, you'll, with a smile on your face, look back to your former self, and laugh at your crazy, cowboy ways. That messy, untestable spaghetti code that you might have snuck into your project in the past will never happen again. In fact, it's quite possible that your codebase, as it currently stands, is untestable! What you may not realize is that, while, yes, testing does help to ensure that your code works as expected, following this pattern will also make you a better developer. The only problem is that testing can be a tricky thing. Sure, you might have read a TDD book in the past, but, like many things in life, we require real-life experience, before we suddenly - in a wonderful, blissful "aha moment" - get it. Before long, you begin to drown, as your ability to manually test the application becomes unrealistic, or even impossible! It's at these specific times, when you begin to realize the down-right necessity for testing. As your application grows, so does your sloppy, untested codebase. Please note that this book exclusively covers Laravel 4.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |