Acceptance testfurureinmind

1,540 views
1,482 views

Published on

Published in: Business, Technology
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,540
On SlideShare
0
From Embeds
0
Number of Embeds
1,072
Actions
Shares
0
Downloads
12
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • Acceptance testfurureinmind

    1. 1. Cucumber Acceptance Tests Lessons Learned
    2. 2. Cucumber Acceptance Tests Lessons Learned A Frightening Journey Inside Cheezy’s Mind
    3. 3. Life is good
    4. 4. Starting Point
    5. 5. What should the testers do?
    6. 6. TesterDeveloper Project Ping Pong
    7. 7. The true cost of a defect Code Test
    8. 8. The true cost of a defect Code Test
    9. 9. The true cost of a defect Code Test
    10. 10. The true cost of a defect Code Test
    11. 11. The true cost of a defect Steps Code Test
    12. 12. The true cost of a defect Steps Code Test
    13. 13. The true cost of a defect Review / Prioritize Steps Code Test
    14. 14. The true cost of a defect Review / Prioritize Steps Code Test
    15. 15. The true cost of a defect Review / Describe Prioritize Steps Code Test
    16. 16. The true cost of a defect Review / Describe Prioritize Steps Code Test
    17. 17. The true cost of a defect Review / Describe PrioritizeReproduce Steps Code Test
    18. 18. The true cost of a defect Review / Describe PrioritizeReproduce Steps Code Test UpdateFix Defect Retest Document
    19. 19. Capers JonesSoftware Assessments, Benchmarks, and Best Practices Addison-Wesley, 2000
    20. 20. What else?
    21. 21. What else?• Unhappy Customers
    22. 22. What else?• Unhappy Customers• Demoralized Demotivated Team • Team Flight
    23. 23. What else?• Unhappy Customers• Demoralized Demotivated Team • Team Flight• Pressure
    24. 24. QA Went Beyond Spec
    25. 25. Testing cut short We have a date to makeso testing needs to end now!
    26. 26. Manual Testing (not ET)1
    27. 27. Manual Testing (not ET) 1.51
    28. 28. Manual Testing (not ET) 2.2 1.51
    29. 29. Manual Testing (not ET) 6.4 5.3 4.0 3.0 2.2 1.51
    30. 30. Automation Fails “Record / Playback testing tools should be clearlylabeled as training wheels” - Elizabeth Hendrickson
    31. 31. First attempts at automationjust automated manual tests
    32. 32. First attempts at automationjust automated manual tests yielding brittle tests!
    33. 33. Little or NoCollaboration
    34. 34. 3 Letter Word
    35. 35. 3 Letter Word 4 Letter Word
    36. 36. Our testers are not verygood because we have way too many bugs!
    37. 37. Hardening Phase
    38. 38. Fear
    39. 39. Bug List
    40. 40. “Cheezy”Coach Extraordinaire (with a dirty little secret)
    41. 41. Leave QA Alone
    42. 42. Testing was constraint
    43. 43. Tester Mr. T
    44. 44. I can handle anything thatfool Cheezy can throw at me!
    45. 45. Thought Process?
    46. 46. Thought Process?• Mr. T is very strong
    47. 47. Thought Process?• Mr. T is very strong• He can be quite intimidating
    48. 48. Thought Process?• Mr. T is very strong• He can be quite intimidating• Did he intimidate the defects out of the system?
    49. 49. Thought Process?• Mr. T is very strong• He can be quite intimidating• Did he intimidate the defects out of the system?• Did the approach actually work?
    50. 50. The Dogs
    51. 51. Early attempts were not always successful
    52. 52. Repeating Mistakes
    53. 53. Repeating Mistakes Test App
    54. 54. Repeating Mistakes Test Test Test Test Test Test Test App Test Test Test Test Test Test
    55. 55. Repeating Mistakes App
    56. 56. Repeating Mistakes App
    57. 57. Works in the small
    58. 58. Large Project Fail
    59. 59. Hard to understand
    60. 60. Hard to understand
    61. 61. Communication?
    62. 62. Kinda makes you sad:(
    63. 63. Success at last!
    64. 64. What is it?
    65. 65. Acceptance Test Driven Development
    66. 66. Acceptance Test Driven Development Behavior Driven Development
    67. 67. Acceptance Test Driven Development Behavior Driven DevelopmentExecutable Specifications
    68. 68. Acceptance Test Driven Development Behavior Driven DevelopmentExecutable SpecificationsSpecification by Example
    69. 69. What did we learn?
    70. 70. The words friggin’ matter
    71. 71. Collaboration is the goal
    72. 72. Automation is necessary (and easy)
    73. 73. Quality is a team sport
    74. 74. Getting the words right
    75. 75. Getting the words right was the hardest part
    76. 76. Speak it!
    77. 77. Collaboration
    78. 78. We discovered walls were still standing
    79. 79. Done Done is Evil
    80. 80. We Need Automation
    81. 81. We Need AutomationStarted off thinking it was all about automation
    82. 82. We Need AutomationStarted off thinking it was all about automation Initially automated too much
    83. 83. Focus on BehaviorConversion of manual scripts == FAIL
    84. 84. Brittle test
    85. 85. Brittle test
    86. 86. Brittle test
    87. 87. Engineering Principles
    88. 88. Engineering Principles Test code is production code!
    89. 89. Engineering Principles Test code is production code!Keep it clean
    90. 90. Engineering Principles Test code is production code!Keep it clean Keep it D.R.Y.
    91. 91. Engineering Principles Test code is production code!Keep it clean Keep it D.R.Y. Build abstractions
    92. 92. Clean D.R.Y. Test
    93. 93. Tools Goals
    94. 94. Tools GoalsMake it very easy to adopt and simple to use
    95. 95. Tools GoalsMake it very easy to adopt and simple to use Provide “template” for code
    96. 96. Tools GoalsMake it very easy to adopt and simple to use Provide “template” for code Make it simple to update as app changes
    97. 97. Data?
    98. 98. Data?Most data doesn’t matter
    99. 99. Data?Most data doesn’t matter Focus on what matters
    100. 100. Data? Most data doesn’t matter Focus on what mattersProvide defaults for everything else
    101. 101. Nice Picture
    102. 102. Still have a ways to go
    103. 103. Still have a ways to goTest Data Management
    104. 104. Still have a ways to goTest Data Management Parallel Execution
    105. 105. Who should automate?
    106. 106. Who should automate? Specification
    107. 107. Who should automate? Specification Automation
    108. 108. Who should automate? Specification Automation Application
    109. 109. Who should automate? Specification Automation Application Exploration
    110. 110. Who should automate? Specification Automation Application Exploration Specification
    111. 111. Who should automate? Specification Automation Application Exploration Specification Application Automation
    112. 112. Who should automate? Specification Automation Application Exploration Specification Application Exploration Automation
    113. 113. Who should automate? Specification Automation Application Exploration Specification Application Exploration Collaboration Automation
    114. 114. Quality is driven by everybody
    115. 115. How do defects get into software?
    116. 116. How do we get them out?
    117. 117. If you find defects after development you are already too late
    118. 118. IT’S TIME
    119. 119. TO CHANGE
    120. 120. THE WAY
    121. 121. WE WORK!
    122. 122. COLLABORATION
    123. 123. WINS!
    124. 124. Thank You

    ×