(Taken from the testing google blog)
I'd much rather see a test a bit closer to this, where the test is much less coupled to the implementation of the interactions with the collaborating object.
For me, this is a classic example of a test that is highly sensitive(coupled) to the implementation(structure)
kentbeck.github.io/TestDesid…
youtube.com/watch?v=bvRRbWbQ…
I'm curious:
Do you both consider a test written like this to be testing implementation details or not?
“La maintenance” by CodingPartner
«Codez comme si les personnes qui effectueront la continuité de ce code sont des personnes chères à vos yeux»
link.medium.com/Tup8CsAfazb
Inspired by(copied from...) Kent Beck's original TDD book, I've presented this using influence diagrams.
Found the visuals to be helpful, for this and other dynamics. Especially when trying to turn negative loops into virtuous ones
Sharing if that may be of help
Straight out of
youtu.be/Hz1JWzyvv8A?t=150
We do have some Camembert
It's a bit runny sir
Oh I like it runny
