1. Test-Driven
Development
for TYPO3
Oliver Klee, 2012-10-04
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 asafety net
for refactoring

13. Green feels good!

14. Green feels good!

16. Know
your
tools

17. The phpunit extension
has it all

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

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

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

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

22. The phpunit extension
has it all
phpunit (TYPO3 extension)
PHPUnit (PEAR package)
Testing framework for FE & DB
Testrunner Testrunner
(back-end-
module) (CLI module)

23. Let‘s get
some terms
straight

24. Two tests
meet in a
bar ...

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

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

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

28. Two tests
Test meet in a
Assertion bar ...
Test
Test
Test case

29. Two tests
Test meet in a
Assertion bar ...
Test
Test
Test case
Test case

30. Two tests
Test meet in a
Assertion bar ...
Test
Test
Test case
Test case
Test suite

31. The life cycle unit test
of a

32. The life cycle unit test
of a

33. The life cycle unit test
of a
new FooTest();

34. The life cycle unit test
of a
new FooTest();

35. The life cycle unit test
of a
new FooTest();
setUp();

36. The life cycle unit test
of a
new FooTest();
setUp();
/** @test */
lifeIsGood();

37. The life cycle unit test
of a
new FooTest();
setUp();
/** @test */
lifeIsGood();

38. The life cycle unit test
of a
new FooTest();
setUp();
/** @test */
lifeIsGood();
tearDown();

39. The life cycle unit test
of a
new FooTest();
setUp();
/** @test */
lifeIsGood();
tearDown();

40. The life cycle unit test
of a
new FooTest();
setUp();
/** @test */
lifeIsGood();
tearDown();

41. Code test-first

42. Code test-first

43. Code test-first
write
test

44. Code test-first
write
test

45. Code test-first
write write
test code

46. Code test-first
write write
test code

47. Code test-first
write write
test code

48. Code test-first
write write
test code
refactor

49. Code test-first
write write
test code
refactor

51. Use meaningful
unit test names

52. Use meaningful
unit test names
Name the
behavior. classCanBeInstantiated

53. Use meaningful
unit test names
Name the
behavior. classCanBeInstantiated
Mention the
method. setTitleSetsTitle

54. Use meaningful
unit test names
Name the
behavior. classCanBeInstantiated
Mention the
method. setTitleSetsTitle
Name the setSizeWithZeroThrowsException
preconditions. hasTitleForEmptyTitleReturnsFalse

55. Use meaningful
unit test names
Name the
behavior. classCanBeInstantiated
Mention the
method. setTitleSetsTitle
Name the setSizeWithZeroThrowsException
preconditions. hasTitleForEmptyTitleReturnsFalse
Dont‘t use
"works" or
"correctly".

56. Use meaningful
unit test names
Name the
behavior. classCanBeInstantiated
Mention the
method. setTitleSetsTitle
Name the setSizeWithZeroThrowsException
preconditions. hasTitleForEmptyTitleReturnsFalse
Dont‘t use
"works" or measureFrubbleWorksCorrectly
"correctly".

57. Use meaningful
unit test names
Name the
behavior. classCanBeInstantiated
Mention the
method. setTitleSetsTitle
Name the setSizeWithZeroThrowsException
preconditions. hasTitleForEmptyTitleReturnsFalse
Dont‘t use
"works" or measureFrubbleWorksCorrectly
"correctly".