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. 2.21.2014
2. why tests provide more than CODE COVERAGE
3. the BUSINESS VALUE behind a TEST
4. dj daugherty
5. @ddaugher
6. Pillar Technology
7. dj@pillartechnology.com
8. deeper look beyond normal thoughts on testing
9. dig into BUSINESS VALUE
10. dig into BUSINESS VALUE documentation created by tests
11. dig into BUSINESS VALUE documentation created by tests ability to engage developers into the business process
12. dig into BUSINESS VALUE documentation created by tests ability to engage developers into the business process compare requirements over time
13. dig into BUSINESS VALUE documentation created by tests ability to engage developers into the business process remove fear of refactoring compare requirements over time
14. are tests important?
15. > code coverage
16. what is CODE COVERAGE?
17. http://en.wikipedia.org/wiki/Code_coverage
18. http://en.wikipedia.org/wiki/Code_coverage
19. http://en.wikipedia.org/wiki/Code_coverage
20. definition of a test
23. test or test suite
24. why do I care?
25. -deliver features -eliminate defects -business value
26. -deliver features -eliminate defects -business value ! working code.
27. @ a high level (business) -features that work - faster development
28. @ a high level (development) -understand codebase -refactor without fear -commit without fear
29. interestingly… development = business
30. the BUSINESS VALUE of TESTING
31. the BUSINESS VALUE of TESTING document conversation
32. the BUSINESS VALUE of TESTING tests clarify intent
33. the BUSINESS VALUE of TESTING repeatable specs
34. the BUSINESS VALUE of TESTING first consumer
35. the BUSINESS VALUE of TESTING executable code examples.
36. the BUSINESS VALUE of TESTING protect features from change.
37. the BUSINESS VALUE of TESTING understand codebase faster
38. the BUSINESS VALUE of TESTING merciless refactoring.
39. the BUSINESS VALUE of TESTING improve code reuse
40. the BUSINESS VALUE of TESTING good code bad code
41. “imperfect tests, run frequently, are much better than perfect tests that are never written at all.” - M. Fowler
42. be careful!
43. be careful! tests… do no create AWESOMENESS!
44. be careful! poor architecture is just poor
45. be careful! bad tests… are just BAD!
46. be careful! too granular.
47. be careful! too implementation specific.
48. be careful! too broad.
49. be careful! too vague.
50. testing… is an ART!
51. testing… is an ART! a lot of effort.
52. testing… is an ART! if tests are hard to write… code may need work!
53. testing… is an ART! asset of the PRODUCT.
54. value !
55. example
56. so…
57. thanks!
58. Q&A