J. B. Rainsberger (he)Mar 20

I just drafted 1400 words about mock objects (and why you might struggle with them) that have been trying to get out for a long time now. These words might see the light of day, but members of The jbrains Experience are reading them now. ;)

https://experience.jbrains.ca

The jbrains Experience: Affordable personal mentoring to help you start getting unstuck.

You need help, but you can't justify the expense of a full-time coach. Maybe you're not yet sure about buying one-on-one coaching sessions. You're struggling to convince your employer to pay for the mentoring you need. You need more than what the world offers you for free, but your budget doesn't have room for enterprise-level consulting. I would like to help you.

jbrains.ca
Show threadPeter SommerladMar 20

@jbrains i gave a talk "mock objects considered harmful " on a C++ conference.

the worst are mocking frameworks that automate mocking.

Show threadJ. B. Rainsberger (he)

@PeterSommerlad I genuinely don't share this view, but I really want to understand it better.

What's the short version? (To start.)

Mar 24 at 10:32pmWeb
Show threadPeter SommerladMar 25
@jbrains i observed people intensively using mocking frameworks that made them not suffer from the many dependencies they created. thus leading to entangled designs that become hard to change, because the entanglement is represented in the tests. manual mocking at least makes one aware that you have a dependency. also in C++ value types / functional style and compile-time generic code has become more popular in favor of "virtual " leading to fewer direct dependencies.
Show threadPeter SommerladMar 25

@jbrains

slides of my talk at https://github.com/PeterSommerlad/talks_public/blob/main/CPPCon/2017/CPPCon_MockingFrameworks2017.pdf

video can be found as well.

talks_public/CPPCon/2017/CPPCon_MockingFrameworks2017.pdf at main · PeterSommerlad/talks_public

PDFs and other information of my talks in the past - PeterSommerlad/talks_public

GitHub