You are signed in. Close

You are signed out. Close

Thank you. Your subscription has started. Close

Thank you. You will get an email when a new comic comes out. Close

We could not confirm your payment. If you paid, use the link "Sign in" at the bottom of the page. Close

Something went wrong on our side. Please try again in a moment. Close

Previous episode Build artifacts: why you build an app once and ship that same copy

How CI/CD works: why releasing code every day is safer than once a month

Staging vs production: why an app is tested on a copy first

Before new code reaches real users, many teams run it on a full copy of their servers, used only by made-up users. What does that copy catch that thousands of tests could not?

  1. 1 Build 57 goes first to staging: servers set up like production, with the same kind of database and settings, but with made-up neighbours and made-up bookings.stagingproduction57made-upneighbour

    Build 57 goes first to staging: servers set up like production, with the same kind of database and settings, but with made-up neighbours and made-up bookings.

  2. 2 On the runner, every test, even the slow ones, used stand-ins: a fake database and a fake message service. Some problems only show when every part of the app runs together.runnersmall teststand-indatabasestand-inmessage service

    On the runner, every test, even the slow ones, used stand-ins: a fake database and a fake message service. Some problems only show when every part of the app runs together.

The rest of this episode is for subscribers

Subscribe to read every premium episode. You can cancel when you want.

Paid yearly: $99 instead of $119.88

Next episode Continuous delivery: why a release should be one boring button

Share this comic

More comics