[{"_1":2,"_48":-5,"_49":-5},"loaderData",{"_3":4,"_10":11,"_46":-5,"_47":-5},"root",{"_5":-5,"_6":-5,"_7":-5,"_8":9},"user","shoppingCartId","toast","locale","en","routes/_store+/_readers+/email_author.$slug/route",{"_12":13,"_45":-5},"book",{"_14":15,"_16":17,"_18":19,"_20":21,"_22":23,"_24":25},"id","Z2lkOi8vbGVhbnB1Yi9TdG9yZTo6Qm9va1Byb2R1Y3QvMTIyNzk","title","短気なプログラマのためのPHPUnitクックブック","state","published","contactAuthorMethod","email","aboutText","

「今までテストを書いたことがないから、そろそろテストを書かなくては・・・」という、PHPUnitもテストのこともまだ知らないプログラマにとって、一番最初に欲しいのは「何から始めたらよいのか」を知るためのガイドです。

本書は、PHPUnitを使ったテストの書き方を、短時間で知るための小冊子です。これだけ読めば、PHPUnitでテストを書いていけるようになります。

本書が特徴的なのは、ユニットテストの形式的な書き方だけを単純に説明した本ではないということです。本書では、PHPUnitによるテストを、オブジェクト指向の原則に沿った、良いコードへリファクタリングしていくための道具、と位置づけています。その流れに沿って、必要最低限の基礎知識や、実際にありそうなサンプルコードで使い方が説明されています。モック（テストダブル）を使ったテスト、フィクスチャを使ったテスト、APIのテストといった対象ごとのPHPUnitテストの書き方を、小さめの例で簡潔に説明しています。本書を読めば、どのようにテストを書いて行ったら良いのか、方向性をつかむことができるでしょう。

(以下は英語版紹介文です）

Learning how to use PHPUnit doesn't have to suck

Your code is untested and fixing bugs is tedious

You know you need something better, but time just doesn't seem to be on your side. Making things \"right\" is costly and you need to deliver working code NOW.

Writing tests is time-consuming and you're not sure how to fit it in

Tests would be great but there are real deadlines to meet. You can't stop development and churn away for hours just to add tests around what you know already works.

PHPUnit is the unit testing framework of choice, but it's intimidating

It looks hard to use and difficult to understand. You have little-to-no experience with it and just figuring out where to start feels daunting. You're left wondering how you use it to test all this stuff you're responsible for.

You don't have time to slow down development

You need to write solid, bug-free code, but your path is filled with manual tests and an application that breaks every time you change it.

You could go home from work, on-time and happy.

Life would be sweet with a solid set of tests

If you already had tests, you'd probably catch bugs faster.

You could refactor your code ruthlessly

Your tests would tell you when a requirements change broke something.

With tests, you'd push code to production with confidence

No longer would you dread the bug reports. You'd happily make changes knowing that your safety net is there. You'd try out new features guiding yourself with tests.

You can make this happen after reading \"The Grumpy Programmer's PHPUnit Cookbook\"

You'll know exactly how to tackle your existing code.

You'll know how to drive new features with your tests.

You'll write tests that run fast and keep you moving quickly.

","authors",[26,39],{"_14":27,"_28":29,"_5":30},"Z2lkOi8vbGVhbnB1Yi9TdG9yZTo6UHJvZHVjdEF1dGhvci8xMjgxNw","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,{"_14":40,"_28":41,"_5":42},"Z2lkOi8vbGVhbnB1Yi9TdG9yZTo6UHJvZHVjdEF1dGhvci8xMjgxOA","Hidenori Goto",{"_31":43},{"_33":44,"_35":36,"_37":38},"https://secure.gravatar.com/avatar/ba8ecb9f1d269e44056ff4e7dca4c5e0?r=pg&d=mm","currentUser","routes/_store+/_layout","routes/_store+/_readers+/_layout","actionData","errors"]

Email the authors