SmokeTests
summary
A PHPUnit-based harness actually runs 20,000 URLs against live servers from CI, validating status code time to first byte and server header and capturing a short body snippet. The deployment flips an idle server into production only after smoke checks pass. A custom PHPUnit-based concurrent smoke tester cuts runtime (originally 45–50 minutes), surfaces Redis and redirect regressions, and fails fast on slow TTFB or wrong origin so teams can abort and fix before traffic switches.
AI-written summary · about
chapters (25)
- 0:00Introduction
- 1:07Disclaimer
- 2:29Project Architecture
- 3:49ATS
- 4:21Fury
- 4:54Backend
- 8:33Architecture
- 9:11Unit Tests
- 13:40Small Tests
- 16:26How do they work
- 17:28What not to do
- 19:12Concurrent smoke tests
- 20:55Continuous deployment
- 22:45How it works
- 24:25Coding
- 28:35Success and Error Output
- 29:58PHP Unit 6
- 34:52Conclusion
- 36:05Staging
- 37:12Do things differently
- 38:32Do you have better use cases
- 41:07How did you get the entire list of URLs
- 43:29What were the issues with the SmokeTest
- 45:00Frontend feature
- 46:35Post requests
related talks
24mSmoke to avoid Fire
40mMy Symfony functional testing toolbox
17mSmoke signals our journey towards Environment Reliability
45mHighway to Continuous Integration
29mEffective tests and testing effectively
37mSelenium In the Enterprise: What went right, what went wrong (so far)
27mTest Effective Development - End 2 (What) End?
01h 05mMicrotesting