Скачать или смотреть "Using test pain as a design guide" by Barry O Sullivan (@barryosull)

Slides: https://slides.com/barryosull/using-t...

Automated testing is a necessary part of software development, we need it if we intend to release our software with confidence. The problem is that writing and maintaining tests can be a painful process, especially in legacy code. Tests become brittle and awkward to use over time. What we don't realize is that this pain is telling us how our system should be structured, we just need to listen.

In this talk we'll discuss test structure, mocking and system design. We'll then take real test cases and show how we can apply tactical patterns to refactor and express the appropriate design, resulting in an application that is easier to understand and maintain from both testing and business perspective.

===

Barry is a Legacy PHP Web app specialist that believes legacy code doesn't have to be painful... His job is to navigate and change valuable codebases that others are afraid to touch. His end goal is to make the changes required by the business and improve the code so that others can work in the space with confidence.