Right Approaches to Testing in PHP: Or How Quantity Can Break Quality
summary
Covers testing practices for PHP projects, explaining test architecture (E2E, functional, unit, and manual) and why testing is the whole team's responsibility. Compares PHP tools PHPUnit, Codeception, Pest, Behat and external tools like Cypress, Playwright, CodeceptJS, Webdriver Bidi; advises against creating custom test frameworks, shows how to make tests visible via test-management systems, and touches on using AI to help testing.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 6:21Testing beyond code
- 8:29Test architecture
- 12:02Testing levels balance
- 13:29Dev-QA communication
- 15:34Optimizing many tests
- 18:48Test parallelization
- 24:05Modern browser testing
- 29:05Avoid custom frameworks
- 32:37Test monitoring
- 35:46Manual testing role
- 38:32Test maintenance
- 40:18DevOps in testing
- 42:46Testomat demo
- 43:07Q&A
related talks
20mEffective Testing Approaches for your Application with Cecelia Martinez
58mObjects, Testing and Responsibility
50mBuilding Testable PHP Applications
01h 00mPrinciples of Unit Testing
29mEffective tests and testing effectively
56mUnit Testing by Example
57mWhy Your Test Suite Sucks
42mHow Can I Trust My Test Suite?