Lasse Koskela What Does It Do Does It Work

  • View
    869

  • Download
    0

Embed Size (px)

Transcript

  • 1.What does it do?Does it work? QCon London 2008 - An XpDay Sampler Lasse Koskela (c) 2008 Lasse Koskela

2. (c) 2008 Lasse Koskela 3. (c) 2008 Lasse Koskela 4. (c) 2008 Lasse Koskela 5. (c) 2008 Lasse Koskela 6. What does it do?Does it work? QCon London 2008 - An XpDay Sampler Lasse Koskela (c) 2008 Lasse Koskela 7. how do we specify systems? how do we test them?(c) 2008 Lasse Koskela 8. how do we test systems?(c) 2008 Lasse Koskela 9. developer testing bliss xUnit frameworks and patterns mock object libraries, reection capabilities language as common denominator (c) 2008 Lasse Koskela 10. customer testing misery no standard toolset tooling generally not sufcient common denominator? (c) 2008 Lasse Koskela 11. surely there are at leastsome commonalities... (c) 2008 Lasse Koskela 12. tools for customer testingtest tool glue system text vs. tabular imperative vs. descriptive(c) 2008 Lasse Koskela 13. connecting to the system there are certain high-level patterns for interacting with the system, and observing side effects(c) 2008 Lasse Koskela 14. 3+2(c) 2008 Lasse Koskela 15. 1 end to end (c) 2008 Lasse Koskela 16. 2 crawling underthe skin (c) 2008 Lasse Koskela 17. 3 exercising the internals (c) 2008 Lasse Koskela 18. +2(c) 2008 Lasse Koskela 19. 4 stubbing out theirrelevant(c) 2008 Lasse Koskela 20. 5 using testing backdoors(c) 2008 Lasse Koskela 21. how do we specify systems? (c) 2008 Lasse Koskela 22. specication analysisdesignimplementation testing (c) 2008 Lasse Koskela 23. (c) 2008 Lasse Koskela 24. agile specication happens during each iteration adds detail incrementally over time eventually evolves into automated tests (c) 2008 Lasse Koskela 25. tests as specication running tests are ultimately the most accurate description of the system (excluding the system itself) translation steps between a specication and tests introduces translation errors(c) 2008 Lasse Koskela 26. acceptance test driven development select feature specify tests implement automate testsfeature (c) 2008 Lasse Koskela 27. who does what?(c) 2008 Lasse Koskela 28. when does it happen? (c) 2008 Lasse Koskela 29. in other words... testers and programmers need to collaborate more closely development team and customer need to collaborate more closely we need a shared language and medium for doing this!(c) 2008 Lasse Koskela 30. we need an interface... testX tool system...that lets us specify tests inour shared language (c) 2008 Lasse Koskela 31. 3 guiding principles(c) 2008 Lasse Koskela 32. 1 Avoid turbulent interfaces (c) 2008 Lasse Koskela 33. 2 Focus on meaning(c) 2008 Lasse Koskela 34. 3 Involve people (c) 2008 Lasse Koskela 35. thank you (c) 2008 Lasse Koskela