I wrote something about testing at the boundaries of your application and contract testing
https://medium.com/@antodippo/testing-at-the-boundaries-of-your-application-fc78145bee9
#testautomation #contracttesting #testdoubles

Breakdown of test doubles. #testing #testautomation #testdoubles

You can use #TestDoubles (#mockobjects) without using a library/framework just the same as you can use #DependencyInjection without a container.

You don't need to feel stuck, even though I can guess how to reached the point of believing you were.

I routinely see programmers who shy away from using #TestDoubles/#MockObjects in their work. You can find so many strong opinions on the topic!

Let me offer another way to interpret one of the often-cited drawbacks of #TestDoubles and one of the often-cited advantages of testing with "the real thing".

https://blog.thecodewhisperer.com/permalink/a-matter-of-interpretation-with-mock-objects

#lightweight #refactoring

Further to my recent discussion about #TestDoubles/ #MockObjects in design, I remember asking this question at a SoCraTes event in Rochegude, France:

"Are method/function expectations an #OOP disease?"

(Or something similar.)

The short answer seemed to be this: it's quite OO, but maybe not a disease. In FP we sometimes contort ourselves to turn complicated custom workflows into straightforward function composition, and it's not always worth the effort.

#lightweight #evolutionarydesign #tdd

Further to my recent discussion about #TestDoubles/#MockObjects in design, I remember asking this question at a SoCraTes event in Rochegude, France:

"Are method/function expectations an #OOP disease?"

(Or something similar.)

The short answer seemed to be this: it's quite OO, but maybe not a disease. In FP we sometmies contort ourselves to turn complicated custom workflows into straightforward function composition, and it's not always worth the effort.

#lightweight #evolutionarydesign #tdd

Further to this idea, whose videos on "evolutionary design without #TestDoubles / #MockObjects" would you endorse? I mean you really like them. You found them compelling and convincing. They don't have to be free.

#lightweight #EvolutionaryDesign #tdd

https://mastodon.social/@jbrains/109438581624133795

I'm mulling hosting an open discussion about the widespread antipathy towards #TestDoubles ("#MockObjects"), because I'd like to understand more about why others have this and I don't.

I'm worried about doing this, because people can act in a way that I prefer not to experience, especially when we try to discuss such issues.

I'm curious about three things:

- Would you attend this?
- Would you watch a recording of this after the fact?
- How would you handle the "bad behavior" issue?