Download to read offline
Uploaded byAsh Winter
Ash_Winter-DEWT7_V1
This document discusses the author's experience consulting with various organizations to improve their testing capabilities. The author found that reviewing testing independently did not address root causes and that organizations often wanted quick fixes rather than systemic changes. The author eventually realized they needed to take a more holistic systems-thinking approach and focus on root causes rather than superficial solutions. They decided to focus more on systems thinking and become nomadic in their work.
Ash_Winter-DEWT7_V1
- 1. Ash Winter Short stuffhere: @northern_tester Long stuff here: #DEWT
- 2.
- 3. • “Reviewing testingcapability independently of other aspects of an organisation is often like moving deckchairs on the Titanic*”
- 4. I was happy… •Reviewing • Interviewing • Strategising
- 5. Started seeing signs… •Few talked about testing • Structural Constraints • Too much WIP • No Product vision
- 6. A Teaching Hospital •Awesome ward dashboard product • Negative process == negative attitude • Testing as a symptom • Recommended balanced testing strategy
- 7. When I returned… •More (of our) consultants • Minor local testing improvements • Same pain existed
- 8. Next time… • Considerthe system • Root causes • Options not solutions
- 9. Book Publisher • Greatbooks, bad software • 3rd Parties • Wanted more consultants to solve their consulting problem
- 10. I recommended… • Deepsystem changes for external services… • Not more consultants… • Time to celebrate a job well done?
- 11. New directions… • Lesssales that way • I quit • Deeper into systems thinking • Nomadic since
- 12.
- 13.
Editor's Notes
- #10 Not lists - again
- #11 But seriously, technical awareness is massive for testers to enhance testability. Knowing the strengths and weaknesses or a given technology potentially gives you insight into where enhanced testability will make the biggest difference.
- #12 Environments do not equal testability – if you can’t administer one, having more will probably break you. Things are the way they are because they got that way. You cannot build a time machine. Be informed by the past but not a slave to it. Big testability scares those with cash and the team too, start small, ask small, but get a commitment to iterate. In your def of done for example.
- #13 Questions? Yis?
- #14 Gwen (please wave) and I are distilling some of this knowledge and experience (Fails) into the ‘Team Guide to Software Testability’ Its part of a wider series On other oft forgotten ilities like testability If anyone has a tale to tell, please give gwen or myself a holler, we’d love to hear from you