[{"_1":2,"_46":-5,"_47":-5},"loaderData",{"_3":4,"_14":15,"_44":-5,"_45":-5},"root",{"_5":-5,"_6":-5,"_7":-5,"_8":9,"_10":11},"user","shoppingCartId","toast","locale","en","constants",{"_12":13},"paypalClientId","AenrHU49peF-ZUH-Yq7AXLLNZYGUGlml474U16NCjB4ZznmQCEjiliN3whyuVZmkb7VxEzmTALgtKEKE","routes/_store+/_readers+/email_author.$slug/route",{"_16":17,"_43":-5},"book",{"_18":19,"_20":21,"_22":23,"_24":25,"_26":27,"_28":29},"id","Z2lkOi8vbGVhbnB1Yi9TdG9yZTo6Qm9va1Byb2R1Y3QvNDI4NQ","title","Laravel Testing Decoded","state","published","contactAuthorMethod","email","aboutText","

Please note that this book exclusively covers Laravel 4.

I've seen it way too many times. As your application grows, so does your sloppy, untested codebase. 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. 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.

The only problem is that testing can be a tricky thing. 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. That messy, untestable spaghetti code that you might have snuck into your project in the past will never happen again. 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. Welcome to modern software development.

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. This book is as much an introduction to TDD as it is a deep analysis of the Laravel way of testing applications. Updates will be free for life. Prefer a print copy?

Nice Words

\n
Just finished reading @jeffrey_way’s Laravel Testing Decoded. It’s worth at least twice the money I paid for it. Highly recommended.
\n

\n
This is one of the best programming books I've read in quite awhile. So many AHA! moments. 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. Not only does it teach testing, but the examples themselves drill best practices into your psyche. Polymorphism in the usually cliche calculator example? Mocks without my brain bleeding? Happy Gilmore references? Screw O'Reilly, I'll buy everything you write.
\n

\n
I'm sure you hear it a lot, but I pay my bills and make my living off what I learned from you...
\n

\n
I am so impressed. Getting those \"Ahas\" while reading your book. :) Laravel 4 users must read it.
\n

\n
I'm about 1/2 through #LaravelTestingDecoded and it's already probably one of the most valuable programming bookings I've read!
\n

","authors",[30],{"_18":31,"_32":33,"_5":34},"Z2lkOi8vbGVhbnB1Yi9TdG9yZTo6UHJvZHVjdEF1dGhvci80NDU3","name","JeffreyWay",{"_35":36},"avatar",{"_37":38,"_39":40,"_41":42},"url","https://d308did4coypzi.cloudfront.net/avatars/31809/medium/jeffrey-way.jpg?1469303615","styleName","medium","exists",true,"currentUser","routes/_store+/_layout","routes/_store+/_readers+/_layout","actionData","errors"]

Email the Author