Sooner or later, an application will have errors. Some of them will be your fault, or that of a teammate. Others stem from third party libraries you are using. We want to be able to locate the cause of the error as quickly as possible. In this workshop, we will do exercises that will help you debug your applications more efficiently as well as writing them in a way that they get easier to debug.

We will look at the following topics:

- reading stack traces
- how to search through the code base
- writing good exception messages
- development time versus run time exceptions (validate options, e.g. OptionsResolver)
- use logging (monolog channels)
- step by step debugger
- using phpunit to debug
- git bisect


Comments are closed.

Great tutorial! Maybe do the more theoretical stuff which was at the end now, more in the middle so you stay active.

Jurgen Rutten at 18:39 on 26 Jan 2018

Nice tutorial, learned some new things, but not a lot off new stuff for a veteran developer

Excellent go through different ways and tools to troubleshoot and debug!
Thank you David!

Jeroen de Jong at 13:37 on 27 Jan 2018

Great tutorial with nice examples to work on. A thing to take another look at is the development environment, there were multiple people who had some issues with it.

David Buchmann (Speaker) at 14:38 on 27 Jan 2018

Thanks for the kind feedback so far.

I have to admit, i was surprised by the ways the vagrant setup managed to fail. (Not being able to install at all would have been less surprising.) I think next time, I will just tell to have a PHP 7 with web server and MySQL set up, seems like the vagrant box made things harder instead of easier.

Koen Cornelis at 15:37 on 27 Jan 2018

Nice demo

Guy Steels at 12:28 on 28 Jan 2018

Good tips. good workshop.