~/talk

SmokeTests - Why you should try to burn down your production environment

Talkat code.talks 2017 · 2017-09-28..09-29· [php, observability]
name:S. Thoß
links:none on file
slides:none on file

Argues for automated pre-activation checks that actually catch production regressions: a PHP smoke-test library (MIT) using PHPUnit and concurrent curl multi sends many requests concurrently (concurrency = CPU cores − 1), verifies status codes, time‑to‑first‑byte, body length and target server, and halts blue/green activation on failure. Implementation reaches ~25k pages per deployment in ~6 minutes, pushes for 100% code coverage, integrates with CI, and is explicitly built to prevent shipping missing or wrong pages rather than just promising examples.

AI-written summary · about

  1. 0:00Start
  2. 2:37Project Architecture
  3. 7:57Legacy Pages
  4. 8:50Types of Tests
  5. 9:22What Are Unit Tests
  6. 13:29Acceptance Tests
  7. 18:40How the Smoke Tests Work
  8. 22:49Concurrent Smoke Tests
  9. 28:09Build Process
  10. 29:19Smoke Tests Fail
  11. 31:05Smoke Test Your Website
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.