GuidesMethod

Staging: why you don’t test on the live site

By the Banzai Labs teamUpdated on 2 min read

StagingTest, break, fixProductionReal customersSame code, same settings, fake data
Staging receives every version before real customers do.

The path of a version

Every version goes through staging
  1. DevelopmentOn the developer’s machine.
  2. StagingThe client and the team test.
  3. ProductionReal visitors.

Rules that make it useful

  • The same codeThe exact version that will go live, not another branch.
  • The same settingsSame hosting, same versions; only secrets differ.
  • Realistic dataIn volume and shape, but fictitious.
  • Payments in test modePayment services provide test keys.

What to check there

  • Key journeys: sign-up, order, payment, e-mails.
  • Display on mobile and desktop.
  • Speed and console errors.

To automate it: CI/CD. For working with the client: Running a remote digital project.

Frequently asked questions

Should staging be protected?
Yes: a password or restricted access, plus a noindex tag. Otherwise Google may index it and create duplicate content.
Can real data go there?
Not personal data. Use fictitious or anonymised data, in realistic quantity.
Is it expensive?
Often not: a small server or a preview URL per branch, created by CI.

Read next

All guides