Testing · interview question
In a Maven project, where should you define your test dependencies to ensure they are included only in the test classpath?
Multiple choiceMediumchapter-10-curatedpremiumtestingunit-testing-with-junit
Answer and explanation
Correct answer
D. <scope>test</scope>
Why
By setting the test dependencies with <scope>test</scope>, they are included only in the test classpath and not in the main build, preventing unnecessary dependencies from being packaged with the application.
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'?