How to get developers to test
Trish Khoo
Why bother?
Shortens feedback loops - faster releases
Creates higher quality code
Frees up testers’ time to find tricky issues instead of no-brainers
Transparency. Predictability. Productivity.
Triangle
Steps
Listen
I’ve heard all of these and more, but everyone still thinks their situation is special and different. That’s okay because everyone’s situation IS special and different, it’s just not so different that it can’t be solved. But if I don’t listen to them, why should they listen to me?
Software is hard. Acknowledge that, empathise, and be an ally. Our job is to make it a bit easier. Developers testing does make it a bit easier.
Know the ecosystem
Who’s in charge? Who’s applying the pressure?
What do they care about? How will adding tests make this person’s life easier?
Where are the risks and safety nets in the process?
Predictability
Strategy
Context
Create a vision
Use tools to make the transition easier
Create a realistic timeline with interim stages
Make sure existing automation is decent, or at least have a plan to make it better. Nobody wants to take over a pile of crap.
Include what to do with testers
Training
When have developers had a chance to learn testing? Most often, never. Most often, devs don’t know how to test and they don’t know how to learn.
Teach:
Want to know more?
Trishkhoo.com - My consulting website
(link) - Register for Quality Engineering training course
Book coming soon!
@hogfish