Writing PHPUnit tests for TYPO3 extensions

Transcript

1. Writing PHPUnit tests 
 for TYPO3 extensions 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. Test levels http:// fi lipdefar.com/2015/06/tested-be-thy-name.html
19. Unit tests are small and fast
20. Functional tests test how components work together also called integration tests
21. Acceptance tests Codeception Cypress
22. The testing pyramid Unit Functional/
 Integration Acceptance Photo by Eugene Tkachenko on Unsplash: https://unsplash.com/photos/TF47p5PHW18