2017 11 leeds tester gathering - i see no bugs!
•Transferir como PPTX, PDF•
1 gostou•430 visualizações
I don't find bugs, I only describe behaviour. In this talk I'll tell you a story of how changing the conversation about bugs changed my whole approach to testing
Recomendados
Recomendados
Mais conteúdo relacionado
Semelhante a 2017 11 leeds tester gathering - i see no bugs!
Semelhante a 2017 11 leeds tester gathering - i see no bugs! (20)
Mais de Ady Stokes
Mais de Ady Stokes (7)
Último
Último (20)
2017 11 leeds tester gathering - i see no bugs!
- 1. I see no bugs! Behaviour OVER bugs, or how solving a problem changed my whole approach to testing @cricketrulz – adystokes@sky.com - linkedin.com/in/adystokes
- 2. A word from our sponsors @cricketrulz – adystokes@sky.com - linkedin.com/in/adystokes
- 3. A quick favour – Joanne @cricketrulz – adystokes@sky.com - linkedin.com/in/adystokes
- 4. Shameless plugs The big test theory.com mobro.co/adystokes?mc=1
- 5. From this story you will • Hear why I don’t find bugs, I only describe behaviour • Why I think bugs have no real intrinsic value • How changing the conversation changed my whole approach to testing @cricketrulz – adystokes@sky.com - linkedin.com/in/adystokes
- 6. Once upon a time 2005 – England win ashes New way to pay, chip and pin Jerry Springer the Opera on the BBC Dr Who revived – played by Christopher Eccleston 400th Celebration of Guy Fawkes night and… A new test manager… @cricketrulz – adystokes@sky.com - linkedin.com/in/adystokes
- 7. The hope @cricketrulz – adystokes@sky.com - linkedin.com/in/adystokes
- 8. The reality @cricketrulz – adystokes@sky.com - linkedin.com/in/adystokes
- 9. Metric madness: Tester metric: Bugs good Developer metric: Bugs bad Result: Arguments – is/is not a bug Almost instant reduction of quality / speed of delivery Disciplined for talking to a developer! Yes really!!! picture from placementindia.com@cricketrulz – adystokes@sky.com - linkedin.com/in/adystokes
- 10. The rebellion As a – tester who finds an issue When – I find ‘bugs’ Then – I’ll talk about behaviour instead And – there shouldn’t be an argument, just a useful discussion AND, I still talked to developers! @cricketrulz – adystokes@sky.com - linkedin.com/in/adystokes
- 11. The new reality @cricketrulz – adystokes@sky.com - linkedin.com/in/adystokes
- 12. The realisation As an entity ‘bugs’ • have no intrinsic value, • are divisive • and a hindrance to collaboration • So, I will see no bugs. I will only describe behaviour Eureka! Bugs have no value! @cricketrulz – adystokes@sky.com - linkedin.com/in/adystokes
- 13. The reasoning, behaviour over bugs part 1 Bugs - No intrinsic value: Reports are almost always incomplete Infers someone is wrong or has done wrong Duplication of effort as a conversation or demos is needed anyway Records can be used (wrongly) by someone as a measurement @cricketrulz – adystokes@sky.com - linkedin.com/in/adystokes
- 14. The reasoning, behaviour over bugs part 2 Behaviour Intrinsic value: Describing the behaviour adds value allowing us to discuss, clarify and if necessary make some alterations or refactors Risk: Describing impacts adds value in deciding the priority Actionable Insights: alternatives adds value in contributing to the overall quality of the system @cricketrulz – adystokes@sky.com - linkedin.com/in/adystokes
- 15. Behaviour query decision tree Describe /some/ Behaviour Undesirable Desirable Address / Fix Leave (forever or address later) Shut up Ady @cricketrulz – adystokes@sky.com - linkedin.com/in/adystokes
- 16. My conclusions Once I stopped looking for ‘bugs’ a few interesting things happened which changed my whole approach to testing Describing behaviour made it about users, risks and outcomes – not about anyone being wrong Users are more important than requirements so I tested everything not just what the requirements said Risk includes everything, usability, testability, accessibility and so on Behaviour has impacts which can make the software useless to some @cricketrulz – adystokes@sky.com - linkedin.com/in/adystokes
- 17. @cricketrulz – adystokes@sky.com - linkedin.com/in/adystokes
Notas do Editor
- Why I stay. People (committed, passionate, length of service), culture open, agile, passionate, community of practice), opportunity (training, support, global audience/opportunities) Beginning life with some clever software on a computer in a kitchen table in the suburbs of Melbourne in the late 1970s, Computershare has since grown to employ 16,000 people and serve 125 million customers around the world. Despite this astronomical growth, the company has never lost its ‘start up’ culture of pushing the boundaries of innovation and shaking up the financial services industry; nor its focus on using the best technology to deliver certainty, ingenuity and advantage to its clients. Computershare manages billions of pounds worth of assets around the world, providing a unique blend of services
- Sing Happy Birthday to you
- Out dated ideas. Wasn’t just waterfall, he was Niagara Falls! Focus was building silos an documentation. Made a lot of promises.
- Things that sort of met the requirement, give information about opening and closing times, could be discussed sensibly
- Bug reports feel like they have value, but it’s the things that go along with it that that destroys any value
- So, describing behaviour became a simple decision tree
- Leave can be based on risk, impact or added as a refactor story to the backlog
- Useless to some, could be a tick box you can’t populate with the keyboard. Could be language used is too technical or understood by us but not strangers.