[{"_1":2,"_42":-5,"_43":-5},"loaderData",{"_3":4,"_10":11,"_40":-5,"_41":-5},"root",{"_5":-5,"_6":-5,"_7":-5,"_8":9},"user","shoppingCartId","toast","locale","en","routes/_store+/_readers+/email_author.$slug/route",{"_12":13,"_39":-5},"book",{"_14":15,"_16":17,"_18":19,"_20":21,"_22":23,"_24":25},"id","Z2lkOi8vbGVhbnB1Yi9TdG9yZTo6Qm9va1Byb2R1Y3QvNDYzODc","title","The Complementary PHP Testing Tools Cookbook","state","published","contactAuthorMethod","email","aboutText","

You've started down the path of writing automated tests for your PHP code and are starting to get into the \"red-green-refactor\" cycle. Fewer bugs are making it into production and you're starting to appreciate the times when your test suite tells you that you've broken something you weren't expecting to break.

But this is just the beginning of the journey towards having confident deployments of well-tested, well-understood code. As more and more people start thinking about the software development process beyond \"write some code and push it up!\", tools have emerged that offer PHP developers a way to write code where the intent is clearer, the code itself is more consistent, and your test suite actually covers the testing scenarios you are expecting it to.

In \"The Complementary PHP Testing Tools Cookbook\" I'll show you how I use static code analysis, code linting, mutation testing, and continuous integration systems to take things one step further towards the goal of confident deployments of well-tested-and-understood code. PHP might be a big ball of nails that sticks to the internet, but that doesn't mean we can't have code that is confidently doing what we expect it to!

","authors",[26],{"_14":27,"_28":29,"_5":30},"Z2lkOi8vbGVhbnB1Yi9TdG9yZTo6UHJvZHVjdEF1dGhvci80ODQ2NA","name","Chris Hartjes",{"_31":32},"avatar",{"_33":34,"_35":36,"_37":38},"url","https://d308did4coypzi.cloudfront.net/avatars/3914/medium/headshot.jpg?1454095682","styleName","medium","exists",true,"currentUser","routes/_store+/_layout","routes/_store+/_readers+/_layout","actionData","errors"]

Email the author