Testing · interview question
In a large e-commerce system, what is a downside of using too many integration tests compared to unit tests?
Multiple choiceHardchapter-10-curatedpremiumtestingmocking-with-mockito
Answer and explanation
Correct answer
B. Integration tests are typically slower and more complex to set up.
Why
Integration tests are slower because they involve setting up and tearing down real components and dependencies, potentially involving databases and network operations. They are also more complex to write and maintain, which can slow down the development process if overused.
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'?