SmokeTests - Why you should try to burn down your production environment
summary
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
chapters (11)
- 0:00Start
- 2:37Project Architecture
- 7:57Legacy Pages
- 8:50Types of Tests
- 9:22What Are Unit Tests
- 13:29Acceptance Tests
- 18:40How the Smoke Tests Work
- 22:49Concurrent Smoke Tests
- 28:09Build Process
- 29:19Smoke Tests Fail
- 31:05Smoke Test Your Website
related talks
50mBuilding Testable PHP Applications
42mHow Can I Trust My Test Suite?
58mTesting Complex Applications for PHP7
04h 25mFull Live Broadcast
28mDo You Know If Your Service Is Working Properly?...
28mGrowing the PHP Core – One Test at a Time
47mRight Approaches to Testing in PHP: Or How Quantity Can Break Quality
50mPerformance optimization: how do I go about it?
