The document discusses test-driven development (TDD) and agile software development principles. It covers TDD concepts like writing failing tests before code, testing-coding-refactoring cycles, and keeping software design loose. The author advocates for object-oriented analysis and domain-driven design to model the problem domain before writing tests. Collaboration between developers and stakeholders is also emphasized for specification by example and TDD.

1. Teddy Chen
teddy@teddysoft.tw
2019/02/21 @ C. C. Agile #76

2. Copyright@2012-2019 Teddysoft

3. Copyright@2012-2019 Teddysoft

4. Bowling Game
【Kata】?
Copyright@2012-2019 Teddysoft

5. Copyright@2012-2019 Teddysoft
√

6. 從發生的事件來回顧
Bowling Game Kata
Copyright@2012-2019 Teddysoft

7. Copyright@2012-2019 Teddysoft

8. Copyright@2012-2019 Teddysoft
√ √

9. Copyright@2012-2019 Teddysoft
好棒棒，看完規則
就知道程式怎麼寫
才怪

10. • OOAD
– Analysis model
• Use case model
• Domain model
– Design model
– Implementation model
– Test model
– …
• TDD (Specification by Example)
– Testing
– Coding
– Refactoring
Copyright@2012-2019 Teddysoft

12. Key Examples

13. Copyright@2012-2019 Teddysoft
√
√√ √
√

14. Ready to write the first
failing test…
Copyright@2012-2019 Teddysoft

15. One step before writing the
first failing test- Design
Copyright@2012-2019 Teddysoft

17. Now you can write the first
failing test
Copyright@2012-2019 Teddysoft

18. testing coding

19. testing coding

20. refactoring

21. testing coding

22. refactoring

23. refactoring

24. testing coding

25. refactoring

26. refactoring

27. refactoring

28. testing all test passed

29. Copyright@2012-2019 Teddysoft
√
√√
√
√
√
√
√
√
√
√

30. Copyright@2012-2019 Teddysoft

31. Copyright@2012-2019 Teddysoft
√
√√
√
√
√
√
√
√
√
√
√

32. Ubiquitous Language and
Bounded Context
Copyright@2012-2019 Teddysoft

33. Copyright@2012-2019 Teddysoft

34. Copyright@2012-2019 Teddysoft
√
√√
√
√
√
√
√
√
√
√
√
√
√

35. Copyright@2012-2019 Teddysoft
PS
1
Test cases
(Verified)
T
Program
(Observed)
Specification
(Expected)
2
4
5 6
3
7

36. Copyright@2012-2019 Teddysoft
√
√√
√
√
√
√
√
√
√
√
√
√
√
√

37. Copyright@2012-2019 Teddysoft
√
√√
√
√
√
√
√
√
√
√
√
√
√
√
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
√

38. 結論
Copyright@2012-2019 Teddysoft

39. • TDD is one way, (but not the only way) to:
– make sure that : (s=t)=p
– keep your software soft
• Do not forget the design part of TDD
– You still need to design the domain model
• OOAD and/or DDD can help
• SBE/TDD needs intensively collaboration
between stakeholders and developers
Copyright@2012-2019 Teddysoft

40. Copyright@2012-2019 Teddysoft

41. • 搞笑談軟工部落格
– http://teddy-chen-tw.blogspot.com
• 搞笑談軟工Facebook
– https://www.facebook.com/groups/teddy.tw
• 泰迪軟體官方網站
– http://teddysoft.tw
Copyright@2012-2019 Teddysoft

42. • Scrum敏捷方法實作班，
http://teddysoft.tw/courses/scrum/
• Design Patterns這樣學就會了–入門實作班，
http://teddysoft.tw/courses/design-
patterns-1/
• Clean Architecture實作班，
http://teddysoft.tw/courses/clean-
architecture/
• 軟體重構入門實作班，
http://teddysoft.tw/courses/refactoring/
• 單元測試這樣學就會了實作班，
http://teddysoft.tw/courses/ut-ci/
Copyright@2012-2019 Teddysoft