Your SlideShare is downloading. ×
Test-driven development
  for TYPO3




Oliver Klee, T3CON10-Frankfurt
Why write
unit tests?
Green feels good!
Green feels good!
Manual testing is cumbersome
Automated
testing is
fast
Unit tests for the
 Realty Manager
   extension
more than
1600 tests
in less than 60
    seconds
Verify that your code
does what you expect
Make sure that your
changes won‘t break
           anything
Create a safety net
    for refactoring
Let‘s get
some terms
  straight
Know
  your
 Tools
The phpunit extension
             has it all
The phpunit extension
               has it all
phpunit (TYPO3 extension)
The phpunit extension
               has it all
phpunit (TYPO3 extension)
 PHPUnit (PEAR package)
The phpunit extension
               has it all
phpunit (TYPO3 extension)
 PHPUnit (PEAR package)

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

 Testrunner   Testrunne...
Two tests
meet in a
  bar ...
Two tests
Test   meet in a
         bar ...
Two tests
  Test      meet in a
Assertion     bar ...
Two tests
  Test      meet in a
Assertion     bar ...
  Test
  Test
Two tests
  Test      meet in a
Assertion     bar ...
  Test
  Test
Testcase
Two tests
  Test      meet in a
Assertion     bar ...
  Test
  Test
Testcase
Testcase
Two tests
  Test       meet in a
Assertion      bar ...
  Test
  Test
Testcase
Testcase
 Testsuite
Code   test-first
Code   test-first
Code   test-first

write
test
Code   test-first

write
test
Code    test-first

write          write
test           code
Code    test-first

write          write
test           code
Code    test-first

write          write
test           code
Code    test-first

write          write
test           code



                       refactor
Code    test-first

write          write
test           code



                       refactor
Upcoming SlideShare
Loading in...5
×

Test-driven development with TYPO3 (T3CON10)

2,189

Published on

Slides from the tutorial at the T3CON10-Frankfurt.

Published in: Technology
2 Comments
0 Likes
Statistics
Notes
  • Hi Roland,

    no, this session was not recorded. It was a tutorial, not a talk, by the way (and usually the tutorials are not recorded).


    Oli
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • hi oliver,

    was your talk recorded back then?

    kind regards

    roland
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Be the first to like this

No Downloads
Views
Total Views
2,189
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
0
Comments
2
Likes
0
Embeds 0
No embeds

No notes for slide



































  • Transcript of "Test-driven development with TYPO3 (T3CON10)"

    1. 1. Test-driven development for TYPO3 Oliver Klee, T3CON10-Frankfurt
    2. 2. Why write unit tests?
    3. 3. Green feels good!
    4. 4. Green feels good!
    5. 5. Manual testing is cumbersome
    6. 6. Automated testing is fast
    7. 7. Unit tests for the Realty Manager extension
    8. 8. more than 1600 tests
    9. 9. in less than 60 seconds
    10. 10. Verify that your code does what you expect
    11. 11. Make sure that your changes won‘t break anything
    12. 12. Create a safety net for refactoring
    13. 13. Let‘s get some terms straight
    14. 14. Know your Tools
    15. 15. The phpunit extension has it all
    16. 16. The phpunit extension has it all phpunit (TYPO3 extension)
    17. 17. The phpunit extension has it all phpunit (TYPO3 extension) PHPUnit (PEAR package)
    18. 18. The phpunit extension has it all phpunit (TYPO3 extension) PHPUnit (PEAR package) Testrunner (back-end- module)
    19. 19. The phpunit extension has it all phpunit (TYPO3 extension) PHPUnit (PEAR package) Testrunner Testrunner (CLI (back-end- module) module)
    20. 20. Two tests meet in a bar ...
    21. 21. Two tests Test meet in a bar ...
    22. 22. Two tests Test meet in a Assertion bar ...
    23. 23. Two tests Test meet in a Assertion bar ... Test Test
    24. 24. Two tests Test meet in a Assertion bar ... Test Test Testcase
    25. 25. Two tests Test meet in a Assertion bar ... Test Test Testcase Testcase
    26. 26. Two tests Test meet in a Assertion bar ... Test Test Testcase Testcase Testsuite
    27. 27. Code test-first
    28. 28. Code test-first
    29. 29. Code test-first write test
    30. 30. Code test-first write test
    31. 31. Code test-first write write test code
    32. 32. Code test-first write write test code
    33. 33. Code test-first write write test code
    34. 34. Code test-first write write test code refactor
    35. 35. Code test-first write write test code refactor

    ×