This document discusses unit testing for the TYPO3 CMS 4.x core. It explains why writing unit tests is important to verify code works as expected, prevent code from being broken, and allow for safe refactoring. It provides an overview of the phpunit testing framework and tools available in TYPO3 for running tests. Finally, it promotes a test-first development approach of writing tests before code.

1. Unit testing for the
TYPO3 4.x core
Oliver Klee, T3DD10

2. Why write
unit tests for
the Core?

3. Verify that your code
does what you expect

4. Make sure people
won‘t break
your code

5. Create a safety net
for refactoring

6. „Reviewing patches is
like cleaning other
people's bathroom“
(OH)

7. Get your
patches
reviewed
more
quickly

8. (and write
easy-to-read,
well-
documented,
well-formatted
patches)

9. Let‘s get
some terms
straight

10. The phpunit extension
has it all

11. The phpunit extension
has it all
phpunit (TYPO3 extension)

12. The phpunit extension
has it all
phpunit (TYPO3 extension)
PHPUnit (PEAR package)

13. The phpunit extension
has it all
phpunit (TYPO3 extension)
PHPUnit (PEAR package)
Testrunner
(back-end-
module)

14. The phpunit extension
has it all
phpunit (TYPO3 extension)
PHPUnit (PEAR package)
Testrunner Testrunner (CLI
(back-end- module)
module)

15. Two tests
meet in a
bar ...

16. Two tests
Test meet in a
bar ...

17. Two tests
Test meet in a
Assertion bar ...

18. Two tests
Test meet in a
Assertion bar ...
Test
Test

19. Two tests
Test meet in a
Assertion bar ...
Test
Test
Testcase

20. Two tests
Test meet in a
Assertion bar ...
Test
Test
Testcase
Testcase

21. Two tests
Test meet in a
Assertion bar ...
Test
Test
Testcase
Testcase
Testsuite

22. Code test-first

23. Code test-first

24. Code test-first
write
test

25. Code test-first
write
test

26. Code test-first
write write
test code

27. Code test-first
write write
test code

28. Code test-first
write write
test code

29. Code test-first
write write
test code
refactor

30. Code test-first
write write
test code
refactor