A team is developing a large-scale platform that consists of several microservices applications. The deployment of each component must take place independently. After each change, checks must be perfo

Smoke tests are a subset of test cases that cover the most important functionalities of a component to ascertain if the deployed build is stable enough to proceed with further testing or usage. They are quick, high-level checks designed to verify that the most critical functions work after a new deployment, ensuring no immediate regression or breakage.

Performance tests evaluate system responsiveness, stability, and resource usage under various loads, which is typically a later, more extensive testing phase, not a quick check after every change for basic impact.

Canary deployment is a strategy to reduce risk by gradually rolling out a new version to a small subset of users before a full rollout, not a type of test performed by a CI/CD tool for basic functionality verification.

Security tests focus on identifying vulnerabilities and weaknesses in the system, which is a specialized type of testing and not the primary method for quickly verifying functional impact after every small change.