I’ve been trying to help people test their PHP code for a very long time, probably before some of you reading this even got started in programming. PHPUnit didn’t exist, the most commonly-used version of PHP was 5.0, and social media wasn’t a thing. GMail had just started being used. My first search engine was Altavista. Yes, I learned to test uphill, both ways, in the snow.

I feel that testing, as a concept, is hard to explain to beginning programmers: “we are going to write code that is going to make sure your other code works as expected”. The assumption that underlies all this is that you already understand how to write computer programs in your chosen language! This makes it very difficult to teach to beginner or inexperienced programmers. When you combine this with how PHP does not force any particular structure on you, you have an environment where only the folks who are really motivated end up learning about testing.

The Grumpy Programmer's Guide To Testing PHP Applications is my way to try and provide some help for developers who are looking to become more test-centric and reap the benefits of automated testing and related tooling like static analysis and automation. I believe that by learning the skills (both technical and core) surrounding testing you will be able to write tests using almost any testing framework and almost any PHP application.

The book combines all the material from my previous books, adds new material, and revisits some old topics where my experiences have changed my thoughts. I break the vast topic of testing into smaller chunks, along with providing lots of examples and explanations of how I approach testing applications. Some of the things I cover are:

• Test-Driven development
• Strategies for Test-After practices
• Test refactoring strategies
• How PHPUnit itself works
• Complementary tools and approaches like static analysis and mutation testing
• Learning the core skills you need to get other people testing their code

The Grumpy Programmer's Guide To Testing PHP Applications is designed to be the book you refer to over and over again to not only learn how to test your PHP applications but to also remind yourself about techniques and tools that lead to successful outcomes. All I've ever wanted to do is get more people testing their code so we can concentrate on solving problems instead of constantly fixing bugs that we might've caught earlier.

How should we decide what kinds of tests to write for our React applications, and how many of each kind? How can we write a test suite that gives us confidence rather than just giving us busywork? Instead of tests slowing down our development, could they actually help us go faster?

Outside-In React Development tackles these questions by applying the practice of outside-in test-driven development (TDD) to React applications. It explains the problems that agile software development solves, the key role that test-driven development plays, and the way outside-in test-driven development helps end-to-end tests and unit tests to work together.

The main part of the book is an extended exercise building a React front-end application from scratch using outside-in TDD. You'll learn:

• How and why to get your app tested on CI and automatically deploying before the first feature is written
• How to use the two-level TDD loop to stay laser-focused on building out one user-deliverable feature to completion
• How to write tests that provide maximum safety with minimum ongoing cost by testing the interface instead of the implementation
• How to get thorough coverage of edge cases while keeping your test suite fast