In a CI/CD pipeline, all automated unit tests have passed during the build stage. Why is the artifact typically deployed to a separate integration environment next?
To validate how the new code interacts with databases, external APIs, and other system components before it moves further down the pipeline.
To rerun the same isolated unit tests that were already executed in the build stage.
To archive previous versions of build artifacts for regulatory compliance only.
To provide the final live environment where end users access the application.
The integration environment exists to expose issues that unit tests cannot detect. Deploying the build into an environment that contains real (or realistic) databases, APIs, message queues, and other shared services validates how the new code interacts with external components and with code produced by other teams. This step helps uncover subtle configuration or compatibility problems early, preventing unexpected failures later in staging or production.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is the purpose of unit testing in a CI/CD pipeline?
Open an interactive chat with Bash
Why is an integration environment different from the build stage?
Open an interactive chat with Bash
What are some common issues identified during integration testing?