More Testable Code with Hexagonal Architecture (Talk)
Video recording of my presentation to PhillyXP on how Separation of I/O Concerns makes code more testable.
The Video
Recently at PhillyXP (remote), I gave an updated version of my talk on how Hexagonal Architecture—primarily its separation of concerns—helps make code more testable. If you’ve seen past versions of this, you’ll want to see this one. I’ve shifted the focus a bit to focus more on tests and what we want out of them. I’m also using my new language for describing tests: I/O-Free Tests (sometimes known as unit tests) and I/O Tests (sometimes matches what people call integration tests). I’ll be writing more about the difference, because I think we often get too hung up on “what’s a unit?” instead of “what kind of test would be useful here?”
Thanks to Anthony and the PhillyXP community for hosting me and asking great questions!
The Course
There’s only so much I can fit in an hour or so, and so I built a 15+ hour course that dives deep into all aspects of making code more testable and refactoring to Hexagonal Architecture. Sign up here to find out when the course is on sale again.
Download the Slides
Click here to download the slides from the presentation.
Discuss
Want to talk about the presentation? Have questions? Join us on the Discord.