Einführung Test-driven Development
1 like654 views
Timo Stollenwerk gave a presentation on test-driven development (TDD) at a Python Barcamp in April 2013. TDD involves writing tests before writing code so that code is only written to pass failing tests, ensuring code works as intended. Following a TDD process results in code that works, is proven to work through testing, has a lower defect rate since it is tested, and is cheaper to fix bugs in. TDD also allows for shorter development cycles and a faster development process since testing is built-in, and makes development more satisfying and fun. Stollenwerk recommended following the practices of no code without a failing test, making the test pass quickly, then refactoring code and tests.
Einführung Test-driven Development
- 1. Test-Driven Development Python Barcamp – April 2013 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 Pyramid
- 17. Unit Testing
- 18. Integration Tests ● Schema ● Factory Type Info ● Factory ● Adding ● View
- 20. Functional Tests ● „Second line of test defense.“ (Martin Fowler) ● Testable specification ● Failure in a functional test > missing unit test
- 22. Test-Driven Development contact@timostollenwerk.net twitter: @timostollenwerk irc: tisto Timo Stollenwerk