@PeterSommerlad@mastodon.social
Post #1386668
2026-03-25 06:30 UTC
@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.
Replies (1)
-
@jbrains@mastodon.social 2026-04-14 17:44
@PeterSommerlad Aha! This is one of the arguments I expected: perfume hides the smell, so we won't clean the room. I simply can't attribute this failure to the mocking framework any longer. That is not the problem. That said, we can't ignore behavioral economics. So... what are the signals of dependency problems, even when mocking libraries do all the boring stuff? Things such as long tests, too many details in one test, and tests failing for strange reasons.