Please enable JavaScript.

Coggle requires JavaScript to display documents.

Testing anti-patterns - Coggle Diagram

- - - - Imagine code that mocks a third party lib. After a particular upgrade of a third library, the logic might change a bit, but the test suite will execute just fine, because it's mocked. So later on, thinking everything is good to go, the build-wall is green after all, the software is deployed and... Boom.
      - Also another issue is that the third party lib might be complex and require a lot of mocks to even work properly. That leads to overly specified tests and complex fixtures, which in itself compromises the compact and readable goal. Or to tests which do not cover the code enough, because of the complexity to mock the external system.
      - It may be a sign that the current design is not decoupled enough from this third party library.