Test-driven development with PHPUnit

1. Test-driven 
 Development 
 with PHPUnit Oliver Klee, 2023-08 @oliklee@chaos.social | typo3-coding@oliverklee.de
2. About me Oliver „Oli“ Kle e #bon n #extension-de v #workshop-teache r #unit-testing-gu y #phpstan-gu y #best-practices-tea m #motivation-research-tea m #team-leadership-working-grou p #game-cookin g #powermetal
3. Unit
 Tests?
4. Manual testing is cumbersome
5. Automated
 testing 
 is fast
6. Unit tests for the 
 TYPO3 Core
7. Unit Tests
 406 (144) tests/s
8. Functional Tests
 8.13 (1.97) tests/s
9. Acceptance Tests
 .009 (.003) tests/s
10. Verify that your code does what you expect
11. Make sure that 
 your changes won‘t
 break anything
12. Keep others 
 from breaking your code
13. Don’t break anything 
 even in complex 
 projects
14. Create a safety net for refactoring or for TYPO3, PHP or Symfony updates
15. Improve the structure of your code
16. Find the location of bugs
17. Green feels good!
18. Let’s get
 some terms
 straight
19. The two programming modes clean hacky
20. Testsuite Testcase Test Assertion Test Test Testcase
21. The life cycle of a test new FooTest(); setUp(); /** @test */ lifeIsGood(); tearDown();
22. 4 test phases set up setUp()
 code in the test method exercise method call verify assert…() tear down tearDown()
23. Code test-first write
 test write
 code refactor
24. Effects of TDD higher code coverage minimale 
 code think before you code tests now test what the code should do (instead of what it does) focused coding cleaner code structure
25. Test levels http:// fi lipdefar.com/2015/06/tested-be-thy-name.html
26. Unit tests are small and fast
27. Integration tests test how components work together in TYPO3: 
 „functional tests“
28. Acceptance tests Codeception Cypress
29. Test types
30. Blackbox tests test the public API
31. Whitebox tests inner workings test the
32. Anti- 
 zombie tests-
33. Regression tests
34. Smoke tests
35. Smoke tests
36. Story tests for Behavior-driven developmen t (BDD) Behat Codeception
37. The testing pyramid Unit Functional/
 Integration Acceptance Photo by Eugene Tkachenko on Unsplash: https://unsplash.com/photos/TF47p5PHW18
38. Naming
 Tests
39. Use meaningful test names classCanBeInstantiated setTitleSetsTitle setSizeWithZeroThrowsException hasTitleForEmptyTitleReturnsFalse Name the behavior. Name the preconditions. Name the method. Don’t use 
 “works” or 
 “works correctly”. measureFrubbleWorksCorrectly