Failing: The Very Human Side of Testing
•
0 gostou•1,971 visualizações
Presentation given at Let's Test 2013, 22 May
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Destaque
Semelhante a Failing: The Very Human Side of Testing
Semelhante a Failing: The Very Human Side of Testing (20)
Último
Último (20)
Failing: The Very Human Side of Testing
- 1. Failing: The Very Human Side of Testing Simon Morley @YorkyAbroad http://testers-headache.blogspot.com/ Wednesday, May 22, 13
- 2. This is about failure.... My experiences Some learnings Wednesday, May 22, 13
- 3. Being Wrong (testing) Anybody ever been wrong? How did it feel? Wednesday, May 22, 13
- 4. My take Frustrating - at first Then - liberating Wednesday, May 22, 13
- 5. But first frustration... Wednesday, May 22, 13
- 6. Communication Test Strategy Communication Talking about a less linear approach - and more focus on business needs and information flow. What could possibly go wrong???? Wednesday, May 22, 13
- 7. Moving from... Wednesday, May 22, 13
- 8. To... Wednesday, May 22, 13
- 9. “But surely if we had clear requirements...” The requirements can’t always be known upfront Clear is very subjective And so are requirements It’s a form of not dealing with the problem - what will satisfy the customer? Wednesday, May 22, 13
- 10. Lessons? Wednesday, May 22, 13
- 11. Different Audiences Familiarity Adoption Refusal / Not prepared Wednesday, May 22, 13
- 12. “But surely if we had clear requirements...” Wednesday, May 22, 13
- 13. And there’s more.... Wednesday, May 22, 13
- 14. Thinking & Models Attention to details - too focused Problems with notetaking Questions / Not getting started quickly enough Getting stuck in a rut Wednesday, May 22, 13
- 15. Attention to details - too focused Wednesday, May 22, 13
- 16. Browsing or client? Wednesday, May 22, 13
- 17. Wednesday, May 22, 13
- 19. Lessons Pair-up Remind yourself: Is it time to switch between focus-defocus now? Wednesday, May 22, 13
- 20. Note Taking I filed a bug report - and missed out a configuration element (parameter setting) that turned out to be decisive. Kneejerk reaction: Take more notes! Or: Take better notes... How? Practice observation & Notetaking Smith: How to be an explorer of the world Wednesday, May 22, 13
- 21. And more... Wednesday, May 22, 13
- 22. Not starting / Too many questions... How? When? By when? Who? Who more can I talk to? What do you mean by test? Anything more? Anything more? Configuration? Data? Architecture? Team? Priority? Risks? Known problems? Wednesday, May 22, 13
- 24. Lessons? Wednesday, May 22, 13
- 25. Start with context-free questions Can I ask some questions? Is now a good time for questions? Ref: Exploring Requirements: Quality Before Design (Gause, Weinberg) Wednesday, May 22, 13
- 26. Sitting with a problem for too long... Wednesday, May 22, 13
- 28. Causes Wednesday, May 22, 13
- 29. Lessons? Wednesday, May 22, 13
- 31. Lessons Fail “well” “The chief trick to making good mistakes is not to hide them - especially not from yourself. Instead of turning away in denial when you make a mistake, you should become a connoisseur of your own mistakes, turning them over in your mind as if they were works of art, which in a way they are.” Dennet: Intuition Pumps and other Tools for Thinking Wednesday, May 22, 13
- 32. More Lessons Celebrate your own failures They are a case study opportunity Ask trusted colleagues for signs Fear of failure = Fear of learning Creativity is bound up with failure Wednesday, May 22, 13
- 33. More lessons Know your audience Synch with them Context-free questions to start with Remember to focus & de-focus Take a step back Explain the problem to someone new Learning is a heuristic activity - implies trial and error Wednesday, May 22, 13
- 34. References Thinking, Fast and Slow (Kahneman) Exploring Requirements: Quality before Design (Gauss, Weinberg) How to Be an Explorer of the World (Smith) Intuition Pumps and Other Tools for Thinking (Dennet) Wednesday, May 22, 13
- 35. Questions & Comments Wednesday, May 22, 13