Specification By Example-A Grange Insurance Story

Transcript

1. SPECIFICATION BY EXAMPLE A GRANGE INSURANCE STORY

2. None
3. None

4. How did we used to communicate?

5. None

6. DEVELOPER JR DEVELOPER

7. Let’s try another approach…

8. None

9. What were upper management’s first reactions?

10. How much will this ? How much will this add?

    I’m skeptical What is the proper ratio? Why do you make that face every time I say “resource”? time   cost   resource  

11. What were the Business Analysts’ first reactions?

12. I’m used to big up front requirements and design. project

    based work breakdown. talking about screens. being the feature gatekeeper.

13. What were Quality Assurance’s first reactions?

14. “You’re automating me out of a job, aren’t you?” “You’re

    asking me to write code!?”

15. How did the Developers react ?

16. Quality is a QA function. I think you guys are

    testing too much. How can ATDD help me? Sweet! So I don’t have to write as many unit tests?

17. so how did we move everyone’s CHEESE?  

18. Understanding everyone’s fears

19. EMPATHIZE

20. Know when to say “I don’t know.”

21. PERSISTENCE AND CONTINUAL IMPROVEMENT

22. Things that worked!

23. Having a business case

24. Cucumber Watir Ruby

25. Getting help early

26. None

27. where are we NOW?  

28. (insert number of tests here)

29. smaller TEAMS

30. BETTER at identifying Acceptance Criteria

31. now writing more DECLARATIVE features

32. Readability Maintainability .feature Files Step definitions Workflows Framework Gems

33. How does upper management feel now?

34. Very encouraged by what they hear from the front lines

    Not only do they support Enterprise-wide adoption, they’re pushing it! Very excited to cautiously optimistic

35. How do the Business Analysts feel now?

36. I’m now slowly sharing control. collaborating while gathering requirements. breaking

    down work as user stories. allowing the product owner to drive features.

37. How does Quality Assurance feel now?

38. collaborating with the team to design the testing approach. able

    to perform exploratory testing. I’m now manually testing things that are difficult to do with automation.

39. How do the Developers feel now?

40. Quality is a TEAM function. Functional and unit test have

    their own purpose. We enjoy having a shared understanding. having a clear definition of “DONE”.

41. where do we go from HERE?  

42. Continue to evangelize and implement ATDD across the organization (and

    Beyond!)

43. Watir-WebDriver: IN PROGRESS

44. Selenium Grid 2: IN PROGRESS

45. PageObject: IN PROGRESS

46. Identify Metrics (because we work in the enterprise)  

47. QUICKIES Communication is hard! Rails Installer = AWESOME git-tfs makes

    TFS bearable Ask us about our Build Pipeline and TFS! (after beers!) Test code is real code Smart Quotes are neither smart nor quotes. Discuss!

48. @andrewvida [email protected] andrewvida.heroku.com @bramhaghosh [email protected]