Stop mocking everything

on YouTube ↗01h 00m

" summary

Claim: stop mocking everything and prefer real implementations where possible. Live PHP code using PHPUnit and PHPSpec builds an overdue invoices calculator with three test invoices, applies 10% interest after 7 days, and shows how mocks force brittle one-to-one coupling: added interactions, nullable due dates, and repo method changes break unrelated tests. A real-memory repo catches a real bug instead of hiding it. Mocks remain recommended for file system database network legacy or costly object-creation scenarios.

AI-written summary · about

" chapters (6)

1. 0:00Start
2. 9:16Php Spec Test
3. 12:56Test Code with the Real Implementation
4. 23:32New Test Code and New Behavior of Calculator
5. 49:06Summary
6. 53:24How Do You Come Up with a Talk

" related talks

• 51mAvoiding MockageddonSebastian Bergmann · PHP fwdays'20 | Special edition
• 59mYour tests are mocking youJakub Zalas · PHP UK Conference 2024
• 50mMocking Dependencies in Unit Tests with PhakeMatthew Turland · PHP UK Conference 2016
• 50mBuilding Testable PHP ApplicationsChris Hartjes · SunshinePHP 2014
• 47m"Testing with Doubles: Why, When, and How?"Sebastian Bergmann · TYPO3 Developer Days 2024
• 52mPlease don’t mock meJustin Searls · Assert(js) 2018
• 28mTo mock, or not to mock?Emily Giurleo · RubyConf 2021
• 41mTesting Legacy Code & Safe RefactoringKaty Ereira · PHP Yorkshire 2019