Change log - Yesterday I gave a talk about PHPStan and code confidence to PHP South West - I’m going to give the talk again: The Symfony user group in Portugal on the 22nd of Feb https://www.meetup.com/pt-BR/sfugaveiro/events/283356907/ North West Drupal User group on the 8th of March https://www.meetup.com/nwdrupal/events/283808251/ - On Tuesday we fixed a unit test which turned out to be a larger issue than I expected and uncovered a big code smell which I need to fix in the coming evenings. - I did a YouTube, Twitter and Discord poll about stopping the music whilst live coding. I will leave the poll going until the end of the week but so far it looks like you lot prefer silence when I code. The stages of bug fixing 1. Investigation and discovery 1. Sometimes its like looking for small patterns in the chaos 2. Do you have all the details needed to reproduces the bug 1. Is there a specific user account or user state needed 2. Is there a specific DB setup needed 3. Is your local environment setup correctly to replicate this issue 4. Is it frontend or backend issue. 5. How often does this bug occur. Is there a pattern to when and how it happens 6. What is the repercussions if the bug is not fixed 7. Has anything recently been deployed that may of caused this issue 8. Is this bug part of a wider ongoing issue that is out of your control 9. Are there any stack traces or log reports that you can see 10. How many entry points does this bug have 11. Can this bug be fixed 12. Should this bug be fixed 13. How long is it going to take. - Include discovery time 14. Do you have approval to work on the fix 2. Testing and verification 1. Can you write a test that replicates the bug in an automated fashion 1. Unit test 2. Acceptance test 3. Fixing 1. Make sure the test is failing 2. Write a fix that passes the test 3. Could this bug be picked up during CI? 1. Does the CI need to be updated 4. Do you need to document the fix 5. Create a PR 6. Does the PR need to be reviewed and approved 7. How are your branches structured 8. Is there a process to release the code and get it tested 9. Does this fix highlight other issues in the system 10. Is this fix temporary 11. For visual fixes, does this break other browsers and displays outside the scope of the testing requirements 4. Testing and verification 1. Does it need to run through QA/UAT 2. Have you added/updated the adequate steps to reproduce 3. Does QA need to update their automated tests scripts 4. Has QA/UAT spotted anything else 5. Can this bug happen outside of the scope of the testing requirements 6. Does this fix require regression testing of other parts of the application 5. Deployment 1. Is this a hot fix 2. Do you need to let your end user know 3. Is there a protocol to follow when a bug is fixed 4. Is there any documentation needed 5. Who needs to be informed Join our Discord server: http://howtocodewell.net/discord Web development courses: https://www.howtocodewell.net/courses Listen to the podcast: https://www.howtocodewell.net/podcast 📖 Related programming courses: PHP Array Course https://www.youtube.com/playlist?list=PLZdsdjcJ44WUWbArkekAHznqfJ60vW8V_ PHP OOP Course https://www.youtube.com/playlist?list=PLZdsdjcJ44WXC5m_8HMcoZft2hmytd4lD JavaScript Array Course https://www.youtube.com/playlist?list=PLZdsdjcJ44WWaBGywrjhXjlJnilh6Z0NX ✉️ Get my weekly newsletter https://email.howtocodewell.net/signup ➡️ Follow How To Code Well: https://www.twitter.com/howtocodewell https://www.twitch.tv/howtocodewell https://www.facebook.com/howtocodewell https://www.instagram.com/howtocodewell #lesson #php #webdevelopment
Please note that we have no copyright's any of the videos shared on our website, any view and revenue playing these videos will goto the owner.
