O slideshow foi denunciado.
Utilizamos seu perfil e dados de atividades no LinkedIn para personalizar e exibir anúncios mais relevantes. Altere suas preferências de anúncios quando desejar.

Shift Testability

216 visualizações

Publicada em

Delivered at NWEWT 3 in Liverpool, using a testability focus to solve testing related problems at their root rather than their symptoms. Focusing on two metrics, "time to start testing" and "unplanned downtime."

Publicada em: Tecnologia
  • Seja o primeiro a comentar

  • Seja a primeira pessoa a gostar disto

Shift Testability

  1. 1. “The most dangerous strategy is to jump a chasm in two leaps.” ~ Benjamin Disraeli
  2. 2. Ash Winter Short stuff here: @northern_tester Long stuff here:
  3. 3. Shift Testability!
  4. 4. Shifting Debate • Left towards development • Right towards operations • Or both!
  5. 5. Courtesy of Cindy Sridharan @copyconstruct TESTABILITY FTW
  6. 6. Hard to Test? • Do more of the testing that testers do • Hiring more testers
  7. 7. Hard to Test? • Moar automation • Making a mockery • Fire and forget into Production
  8. 8. Think Testability! • Observe • Control • Understand • Testable == Supportable • Useful to all not just Dev and Ops!
  9. 9. Heuristics of Software Testability
  10. 10. • Distracted by features… • Where is the biggest gain to be made in the system? Faffing with features?
  11. 11. • Not saying no value… • Testers testing features finds important problems... Disclaimer
  12. 12. • Time taken to start testing • Unwittingly extended and/or unplanned downtime Two Metrics
  13. 13. • Mobile app • Local dev environment • DNS • Hours between pull branch to test on device Time to testing
  14. 14. Time to Testing • Testing was always lagging • Exhausted by the time testing began • Important problems missed
  15. 15. Testability FTW! • Branch to device in minutes • Devs testing on real devices!
  16. 16. • Infra “tribe” • Planned & unplanned downtime • Hiring testers • Build vast environments • Big bangs Costly Downtime
  17. 17. Costly Downtime • Infra problems > feature problems • £250k per hour worth
  18. 18. Testability FTW! • Much more empathy • Lower unplanned/extended downtime
  19. 19. Conclusion!
  20. 20. The Three Ways of DevOps • Amplify Feedback • Experiment & learn • Systems Thinking
  21. 21. Hang on, isn’t that testability? • Observe system feedback • Control system state to hypothesize • Understand whole system, optimise globally
  22. 22. Questions

×