Phase 6 · Module 12 of 15Quadrant D · the change
Testing, Release, and Deployment
How does code safely move from an engineer's computer to customers?
By the end: You can explain the software delivery pipeline and distinguish release from deployment.
L1The four worlds code lives in~7 min○L2Tests that write themselves into the future~8 min○L3The testing vocabulary, complete~13 min○L4The pipeline: from merge to production without hands~8 min○L5Release is not deployment~6 min○L6Undo buttons: rollbacks, hotfixes, and compatibility~6 min○
What lights on your map here
environmentdevelopment environmenttesting environmentstaging environmentproduction environmentbuild (artifact)pipelinecontinuous integrationcontinuous deliverycontinuous deploymentCI/CDunit testingintegration testingend-to-end testingautomated testingmanual testingquality assuranceacceptance testingUATtest datatest coveragemockregression testingsmoke testingperformance testingload testingsecurity testingreleasedeploymentfeature flagrollbackhotfixbackward compatibilitybreaking change
Recognition terms — you'll know they exist
canary releaseblue-green deploymentshadow mode
Named technologies
GitHub Actions