Test-Driven Development with Plone
4 likes2,407 views
This document discusses test-driven development (TDD) with Plone. TDD involves writing tests before code so that code is only written to pass existing tests. This ensures code works as intended and defects are minimized. The document outlines benefits of TDD like shorter development cycles, faster processes, cleaner code, and satisfaction. It also discusses different types of tests like unit tests, integration tests, functional tests, and acceptance tests using Robot Framework. Recommended books on TDD are also mentioned.
Test-Driven Development with Plone
- 1. Test-Driven Development with Plone Plone Conference Arnhem 2012 Timo Stollenwerk
- 2. Testing ???
- 3. Do not break things! Timo Stollenwerk
- 4. What do we get? ● Code that works ● Proof that is works ● Lower defect rate ● Cheaper bug fixing
- 9. What do we get? ● Shorter development cycles ● Fast development process ● Satisfaction ● Fun!
- 10. No code without a failing test
- 11. Make test pass (quickly)
- 12. Test
- 13. Fix
- 14. Refactor
- 15. What do we get? ● Clean Code that works ● Agile code
- 16. Testing in Plone
- 17. Testing Pyramid
- 18. Integration Test: Dexterity Type ● Schema ● FTI ● Factory ● Adding ● View
- 19. Unit Testing
- 20. Mocking
- 22. Functional Tests ● „Second line of test defense.“ (Martin Fowler) ● Testable specification ● Failure in a functional test > missing unit test
- 23. Robot Framework Acceptance Tests
- 24. Robot Framework Acceptance Tests
- 25. There is more...
- 28. Test-Driven Development with Plone Timo Stollenwerk contact@timostollenwerk.net twitter: @timostollenwerk irc: tisto