Dec 23, 2014
Lessons learned in Software Testing
Paula AlixandrovEndava
10.03.2012
Lessons learned in Software Testing
A context-driven approach
Cem Kaner - http://kaner.com/
James Bach - http://www.satisfice.com/blog/
Bret Pettichord - http://www.pettichord.com/
Your mission drives everything you do
What should you do when you don’t know what to do?
What should you do when you know exactly what to do?
Good testers think….
Technically Model technology and understand
causes and effects
Creatively Generate ideas and see possibilities
Critically Evaluate ideas and make inferences
Practically Put ideas into practice
Tester’s tools
You are what you write Good reporting earns…good reputation
DO’s
Report defects promptly
Use the bug summary line to sell your bug to the managers
Keep clear the difference between severity and priority
Pick your battles – not every bug that you report will be fixed
DON’T’s:
Don’t assume that an obvious bug has already been filed
Don’t reword other people’s bug reports
Never write reports that seem blaming, petty in tone, poorly explained, or inadequately researched
Develop mutual respect between you and the programmer
Develop mutual respect between you and the programmer
Assume that the individuals you work with are worthy of respect and act on this assumption
Demonstrate sensitivity, appreciation and diplomacy
Find out what kind of feedback programmers want and give it to them
Refuse to accept mistreat or abuse
Develop mutual respect between you and the programmer
Your integrity and competence will demand respect
Your integrity and competence will demand respect
You are a customer advocate: report credible problems accurately and directly
Don’t pretend to know things you don’t
Don’t exaggerate your reports but stick to your guns
If you have integrity, you can develop your competence
Thank you
Please fill the evaluation form.