From the course: PHP: Testing Legacy Applications
Unlock the full course today
Join today to access over 22,500 courses taught by industry experts or purchase this course individually.
Just how many tests do we need?
From the course: PHP: Testing Legacy Applications
Just how many tests do we need?
- [Instructor] I worked for a company that insisted that everyone needed to stick around whenever a deployment happened, just in case something went wrong. It was terrible for morale, and did nothing to actually solve the problem of an application that would break in unexpected ways. As you can guess, we had no tests in place. So after a lot of lobbying, I got buy-in on test becoming mandatory. But the first question I got was, well, how many tests do we need? If we look at the situation I mentioned, how many tests would we need to make people less worried about a deployment? I think you would want tests for any code that got changed, as proof that it all works as expected. That way you are building confidence that releasing that code for everyone else to see won't be a disaster. Also it made total sense that the whole team needed to be around in case something broke. This was in 2003, before the tools and concepts I talk about were being widely promoted in the PHP world. We literally…
Practice while you learn with exercise files
Download the files the instructor uses to teach the course. Follow along and learn by watching, listening and practicing.