Ce diaporama a bien été signalé.
Nous utilisons votre profil LinkedIn et vos données d’activité pour vous proposer des publicités personnalisées et pertinentes. Vous pouvez changer vos préférences de publicités à tout moment.

Ash_Winter_Tested_to_Death

414 vues

Publié le

  • D0WNL0AD FULL ▶ ▶ ▶ ▶ http://1url.pw/DFVV6 ◀ ◀ ◀ ◀
       Répondre 
    Voulez-vous vraiment ?  Oui  Non
    Votre message apparaîtra ici
  • Soyez le premier à aimer ceci

Ash_Winter_Tested_to_Death

  1. 1. Ash Winter Short stuff here: @northern_tester Long stuff here: Tweet on #AgileYorkshire
  2. 2. Tested to Death… Or how testing can trap you in a team and product death spiral
  3. 3. So, I’m a tester right… • Weird topic • Too much testing is bad • Serving tests is bad • Testing the same thing at different levels can be bad
  4. 4. Pop quiz hotshots… Quick state of the nation. How many of you… • Think you do too much testing? • Think you do too little testing? • Think your testing is effective?
  5. 5. Let me tell you a story… •Fansz •Great dudes assembled •Ready FTW
  6. 6. There was a strategy… You’ve all seen the testing pyramid before right?
  7. 7. Funny business… Unit Tests == Integration Tests == Acceptance Tests
  8. 8. Nosey parkers… Integration tests poked their noses in unit and acceptance tests business.
  9. 9. Weird smells… Change the tests to get the code to pass?
  10. 10. Eyebrows raised… Injected dependencies were mocking us…
  11. 11. Brows furrowed… Lets try other test runners. That will help.
  12. 12. Quicksand… • New stuff? Slow • Change stuff? Slower
  13. 13. Worst of all, sad faces… • Frustrating, endless discussion • Sad dependant teams • Sad sponsors
  14. 14. Ultimately… A Dream (and Team) Expired* *Really not the only reason. Didn’t help
  15. 15. But don’t despair… In life and testing, there is no fail, only learning!
  16. 16. #1 All tests must die • Tests have a life and a death • You CAN kill them ALL! • Be pointy with tests that pass ALL the time!
  17. 17. #2 Chasing sunk cost will sink you • Inventory • 1 line of code, change 800 tests • Think value, not cost
  18. 18. #3 Unit Tests? • Erm • Make sure you are actually writing unit tests
  19. 19. #4 You can write tests first… • Your app is not special • More likely to have only the tests you need
  20. 20. #5 Dependencies You are the child, the dependency is the parent
  21. 21. #6 Checkocalypse Now How many times do you need to check 1 + 1 = 2?
  22. 22. #7 Small • Very small packs of tests that reflect the system • Separate ignored tests • Then destroy them!
  23. 23. #8 Pairing is smart • Two brains write better tests • Hint - Especially a tester and dev
  24. 24. #9 Use more than one model • Marick's Quadrants par example • Too many technology facing tests…
  25. 25. #n Context or ‘it depends’ We weren’t even in beta. (gently weeps)
  26. 26. And in summary… • Testing is great! • Evolve your strategy! • It serves you, not the other way around…
  27. 27. Questions?

×