In the middle of Web 3.0 it's become obvious that a very large percentage of developers are aware that there are tools available that allow them to write automated tests for the code they write. But you don't write tests. Never have. You feel a little bad about it but you tell yourself that it looks really tough to get into and you have a hard deadline that doesn't have any time for you to learn to use these tools.

What if you could learn how to write tests from someone who has been using them for a long time and also knows how to explain it in a way that cuts down on the fear and anxiety while teaching you what you need to go to get started immediately? That's what Chris Hartjes, long-time PHP testing evangelist, wants to do for you.

In this workshop Chris starts you off from the point of never having written a unit test and guides you through what tests really are. Then he will show you PHPUnit works and what features are the ones you really need to know. Next you will walk through using Test Driven Development using some code katas and leave with a solid, practical foundation that you can take back to your regular job and actually use. Testing your code is hard and might require you to relearn some closely-held practices. Let a grumpy programmer fix that for you!

Please come with the following setup and ready:

PHP 7.0.x (whatever the stable version is)
PHPUnit (latest stable)
Mockery (latest stable)
Requirements: This workshops is aimed at developers staring out with testing.


Comments are closed.

Thanks for the talk! Good one, i really liked it. But i wished for more insights. We had enough time for practice, which was great! But more practice for writing the fitting tests would have been better than some exercises that targeted on the programming solution, and not thier tests. So if there would have been a little working app where we have to write tests for, that would have been nice.

And/or an example where we would see more the benefit of TDD, to see how the tests shape the form of the tested object.

Thank you for the workshop and the good mind-changing examples regarding test-driven development!

The only two things I wished to be different are more depth in unit-/integration-testing and especially some real life examples of complex projects like distributed architecture or service dependencies. Maybe you could construct some complex requirements for an app with multiple solution ways for TDD and with some traps and let the students try to solve it. I think there should often be a reason or some punch to realize that something has to change :)