Testing · interview question
Which of the following is NOT a typical use case for Mockito in integration testing?
Multiple choiceMediumchapter-10-curatedpremiumtestingintegration-testing
Answer and explanation
Correct answer
D. Testing UI components.
Why
Mockito is primarily used to mock interactions between services and components. It is not typically used for testing UI components, as those are usually tested with other tools designed for user interface testing.
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'?