In the context of CI/CD, what does 'Continuous Integration' encourage?

In the context of CI/CD, what does 'Continuous Integration' encourage?

• A. It encourages developers to frequently check in code and automatically test their projects prior to release.
• B. It discourages automated testing and favors manual checks.
• C. It recommends delaying tests until after release.
• D. It discourages frequent code changes.

Answer: (A)

Continuous Integration emphasizes merging small, frequent changes into a shared code repository and validating them with automated builds and tests. That means developers are encouraged to check in code often and rely on automated testing to verify that each change integrates correctly before it progresses toward release. Running tests automatically on every integration helps catch defects early, keeps the build healthy, and maintains a deployable state, which is the main advantage of CI in a CI/CD pipeline. The other options would undermine this: delaying tests or favoring manual checks reduces fast feedback and increases risk, and discouraging frequent code changes goes against integrating changes early and often.

Continuous Integration emphasizes merging small, frequent changes into a shared code repository and validating them with automated builds and tests. That means developers are encouraged to check in code often and rely on automated testing to verify that each change integrates correctly before it progresses toward release. Running tests automatically on every integration helps catch defects early, keeps the build healthy, and maintains a deployable state, which is the main advantage of CI in a CI/CD pipeline. The other options would undermine this: delaying tests or favoring manual checks reduces fast feedback and increases risk, and discouraging frequent code changes goes against integrating changes early and often.