Engineer’s Sound Sleep: How We Ensure Quality to Sleep Peacefully
summary
Practical experience writing automated tests (autotests) for PHP systems to prevent surprises in production, and how those tests are integrated into the testing system. Also discusses whether formal documentation is necessary when tests already describe the system.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 2:30Sleepless nights causes
- 5:59Testing bottlenecks
- 7:25QA to developers
- 9:09Unclear task problems
- 10:55Two-stage task prep
- 13:28Automated testing pipeline
- 16:17Manual testing docs
- 19:35Testomat storage
- 20:21Test strategy maturity
- 22:28Deployment monitoring
- 23:52Observability role
- 26:20Alerting and logging
- 27:44Four pillars of peace
- 28:46Key takeaways
related talks
47mRight Approaches to Testing in PHP: Or How Quantity Can Break Quality
35mSleeping better at night
01h 48mNo Such Thing as Manual Testing and Other Confusions
34mBe SOLID my Tests
35mWhy Software Engineers Should Make Quality a Priority
29mEffective tests and testing effectively
51mTesting: Programista, bezpiecznik i automatyczne testy (...)
46mPanel Discussion: Quality Engineering - an Evolution of Software Quality as a Team Responsibility