Project Structure · interview question
In a Maven project, where should you define a dependency that is only needed for testing?
Multiple choiceMediumchapter-10-curatedpremiumproject-structurejava-modules-jpms
Answer and explanation
Correct answer
A. In the <test> scope
Why
Dependencies needed only for testing should be defined in the <test> scope. This ensures they are available in the test phase but not included in the final build product.
Test yourself on Project Structure
A free test with instant, explained results. No account needed.
More Project Structure questions
- Why might you choose to use integration tests despite their higher resource cost compared to unit tests?
- Why do teams use Continuous Integration in software development in production code?
- Which JUnit assertion would you use to verify that a method returns a null value?
- Why is it important to have strong encapsulation in a module system like JPMS?
- Which of the following strategies can prevent a bad merge into the main branch in a CI/CD workflow?
- In a JPMS setup, what happens if a module exports a package but does not specify which other modules can access it?