why tests provide more than code coverage... the business value behind a test.

The session will take a deeper look into the ideas around testing beyond the normal TDD thoughts on tests. We will dig into the business value behind the documentation created by tests, the ability to better engage developers into the business process, the ability to compare requirements over time, and the removal of fear around the practice of refactoring... plus many more. It will be a fun journey allowing developer-types and business-types alike come to a common understanding of why tests are important.

Transcript

1. 11.01.2014 Iowa code camp
2. tests
3. code coverage. are more than why tests
4. the business value behind a test code coverage. are more than why tests
5. dj daugherty
6. dj@pillartechnology.com dj daugherty
7. dj@pillartechnology.com dj daugherty @ddaugher
9. we are hiring !
11. i am developer.
15. think.
16. question the norm.
17. i struggle with these ideas every day.
18. code coverage. why tests are more than the business value behind a test
19. how many developers?
20. how many business?
21. dig into testing
22. documentation. dig into testing
23. engage developers into business process. dig into testing documentation.
24. compare requirements over time. engage developers into business process. documentation. dig into testing
25. remove fear of refactoring. engage developers into business process. documentation. compare requirements over time. dig into testing
26. code coverage? what is
27. http://en.wikipedia.org/wiki/Code_coverage
28. http://en.wikipedia.org/wiki/Code_coverage
29. http://en.wikipedia.org/wiki/Code_coverage
30. test? what is a
33. code or an application
34. why do i care?
35. deliver features. eliminate defects. why do i business value. care?
36. care. deliver features. eliminate defects. why do i business value. working code.
37. @ a high level business
38. @ a high level business features that work. faster development.
39. @ a high level development
40. @ a high level development understand codebase. refactor without fear. commit without fear. understand business.
41. interestingly…
42. development = business interestingly…
43. interestingly… development = business
44. business value
45. business value the of testing
46. conversation. document
47. intent. clarify
48. specifications. repeatable
49. consumer. first
50. code examples. executable
51. protect from
52. faster. understand code
53. refactoring. merciless
54. code reuse. improve
55. bad code. good code
56. “imperfect tests, run frequently, are much better than perfect tests that are never written at all.” - M. Fowler
57. watch your tests
58. tests… do not create AWESOMENESS!
59. poor architecture… is just poor.
60. bad tests… are just bad.
61. bad tests… are just bad. too vague too implementation specific too granular too broad
62. art. testing is an
63. if tests are hard to write… code may need work!
64. product. asset of the
67. testing
68. just start.
69. start. just it will suck at first.
70. start. just it will suck at first. that’s ok.
71. start. just it will suck at first. have a ritual. that’s ok.
72. start. just it will suck at first. have a ritual. it is ok to fail. that’s ok.
73. start. just it will suck at first. have a ritual. it is ok to fail. beer helps! that’s ok.
74. start. it will suck at first. have a ritual. it is ok to fail. beer helps! eventually it will suck less. that’s ok. just
75. thanks. dj daugherty dj@pillartechnology.com @ddaugher
76. Q&A. dj daugherty dj@pillartechnology.com @ddaugher