Test-driven development for TYPO3

Slides of my workshop on T3DD14

Transcript

1. Test-Driven
   Development for TYPO3 Oliver Klee, 2014-06-21 @oliklee typo3-coding@oliverklee.de
2. Unit tests?
3. Manual testing is cumbersome
4. Automated testing is fast
5. Unit tests for the
 Realty Manager extension
6. more than
 1600 tests
7. in less than 60 seconds
8. Verify that your code does what you expect
9. Make sure that your changes won‘t break anything
10. Keep
    other coders
    from breaking your code
11. Don‘t break anything
    even in complex projects
12. Create a safety net
    for refactoring
13. Improve the structure of the code
14. Green feels good!
16. Know your tools
17. The phpunit extension has it all phpunit (TYPO3 extension) PHPUnit (Composer package) Testrunner (back-end- module) Testrunner
 (CLI module) Testing framework for FE & DB
18. Let‘s get some terms straight
19. Test suite Test case Test Two tests meet in a bar ... Assertion Test Test Test case
20. The life cycle of a unit test new FooTest(); setUp(); /** @test */ lifeIsGood(); tearDown();
21. Code test-first write
 test write code refactor
23. Use meaningful
    unit test names classCanBeInstantiated setTitleSetsTitle setSizeWithZeroThrowsException hasTitleForEmptyTitleReturnsFalse Name the behavior. Name the preconditions. Mention the method. Dont‘t use "works" or "correctly". measureFrubbleWorksCorrectly