Library › Book 16 › The Testing Pyramid in CI
The Testing Pyramid in CI
4.1🔒Why Pipeline Structure Mirrors the Test PyramidNot all tests belong at the same stage. The testing pyramid dictates not just what kinds of tests you write, but when they run in your…
4.2🔒Stage 1: On Every Push (Seconds to Minutes)This is the fastest feedback loop. Developers get results before they context-switch away from the code they just wrote.
4.3🔒Stage 2: On Pull Request / Merge to Develop (Minutes)This stage runs when code is proposed for integration. It catches issues that require real infrastructure -- databases, message queues…
4.4🔒Stage 3: On Merge to Main / Pre-Deploy (Minutes to Tens of Minutes)This is the final validation before code reaches users. Run the expensive, thorough tests here.
4.5🔒Stage 4: Post-Deploy (Continuous)After deployment, testing does not stop. Post-deploy checks verify that the application works in the actual production environment.
4.6🔒Mapping Test Types to Pipeline Stages
4.7🔒Common Mistakes in Pipeline Test StructureIf browser tests run on every push, developers wait 20 minutes for feedback on a one-line fix. Run only fast tests on push; save expensive…
4.8🔒Career Translation- Restructured CI pipeline around the testing pyramid, mapping unit, integration, contract, and E2E tests to four pipeline stages with…
4.9🔒Q&AInterview Depth CheckPrompt: Your team has 2,000 unit tests (90 seconds), 150 integration tests (8 minutes), and 80 browser tests (25 minutes). All run on every…