Testing · interview question
Why can mocking internal dependencies too extensively in unit tests become a problem in production code?
Multiple choiceHardchapter-10-curatedpremiumtestingmocking-with-mockito
Answer and explanation
Correct answer
C. It might lead to brittle tests that break with implementation changes
Why
Over-mocking internal dependencies can lead to tests that are tightly coupled to the implementation details. As a result, any changes to the codebase could break the tests, requiring frequent updates and reducing their reliability as a safety net.
Test yourself on Testing
A free test with instant, explained results. No account needed.
More Testing questions
- How can build tools like Maven help manage library dependencies in Java projects?
- Why might you choose to use integration tests over unit tests for certain components in an e-commerce application?
- Which benefit of automated unit testing is most critical for maintaining large Java projects?
- How would you explain a significant advantage of using mocks at the boundary of a system, rather than the internals in…
- Why do teams use Mockito for mocking dependencies in tests in production code?
- In a unit test using Mockito, why would you use 'when-thenReturn'?