Project Structure · interview question
In the context of continuous integration for a Java e-commerce project, how can you ensure that only production-ready code is merged into the main branch?
Multiple choiceMediumchapter-10-curatedpremiumproject-structurecontinuous-integration
Answer and explanation
Correct answer
D. Use a CI pipeline that runs automated tests and requires all tests to pass before merging.
Why
Using a CI pipeline that runs automated tests ensures that code changes do not break existing functionality. Requiring all tests to pass before merging acts as a safeguard against integrating untested or broken code into the main branch. Manual code reviews, while helpful, are not as reliable as automated tests in catching all potential issues.
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?