A presentation at TestBash 2016 in in Brighton, UK by nicola sedgwick
#testbash @nicolasedgwick me. Nicola Sedgwick Tester, Test Manager, Test Coach, Agile Team Member, etc.
“there’s a bug in production” bug.
“there’s a bug in production” “was this tested?” bug.
“there’s a bug in production” “was this tested?” “what did i miss?” bug.
“there’s a bug in production” “was this tested?” “what did i miss?” “how serious is this problem?” bug.
“there’s a bug in production” “was this tested?” “what did i miss?” “how serious is this problem?” “how could i have let this happen?” bug.
we KNOW no-one is placing blame we KNOW our testing process isn’t flawed we KNOW the team did everything ‘right’ rational.
who will trust my testing of the fix? it’s my fault! i’m going to get fired!!! irrational.
do testers need a thick skin? or should we admit we’re simply human?
#testbash @nicolasedgwick easy. “i found a bug by just opening a page and looking at it - i could be a tester”
#testbash @nicolasedgwick testers. [Images from Software Testing Club]
#testbash @nicolasedgwick perceptions. playing devil’s advocate providing information questioning bug advocacy
#testbash @nicolasedgwick value. • “now you’re just nit-picking” • “you’re too critical” • “why not ignore it this once” • “those aren’t REAL bugs” • “but you’re just a tester” • “testers always complain” • “you’re never satisfied” • “testers are just so negative”
#testbash @nicolasedgwick impact. [Yerkes-Dodson law]
#testbash @nicolasedgwick skin. self-esteem: a feeling of having respect for yourself and your abilities imposter syndrome: a collection of feelings of inadequacy that persist despite evident success. confidence: a feeling or belief that you can do something well or succeed at something burn out: exhaustion of physical or emotional strength or motivation usually as a result of prolonged stress or frustration
coral.
#testbash @nicolasedgwick starting point. new child marriage bereavement house move
fight or flight.
#testbash @nicolasedgwick fighting your corner
#testbash @nicolasedgwick exhaustion.
“Thank you for refusing to be ignored - I’d given up highlighting the issue as it just seemed to fall on deaf ears.” vindication.
#testbash @nicolasedgwick caring. vocal invested involved passionate
#testbash @nicolasedgwick manifesto. Individuals and interactions
over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan Extract from Manifesto for Agile Software Development
guard.
#testbash @nicolasedgwick self-help. • eat healthily • sleep properly • get some fresh air • relax your jaw • take regular breaks • don’t dwell on problems • get some exercise • reduce screen time
#testbash @nicolasedgwick de-stress.
#testbash @nicolasedgwick cope. 1. get away; get outside 2. headphones 3. mentors & peers 4. cap your workload
#testbash @nicolasedgwick inspiration
#testbash @nicolasedgwick realise. is one perfect no
motto.
#testbash @nicolasedgwick grow. collaborate share the workload and gain appreciation of other roles heal yourself delivery of information and opinion changes based on mood or situation mirror lead by example - treat others with respect and expect same in return involved be an active team member not a passive information provider
young “i know everything” developer who knew everything and expected testers to simply validate functions on real devices improve.
became a young respected developer fully collaborating with the team, offering assistance to colleagues regardless of role differences and thinking ahead from the outset. improve.
#testbash @nicolasedgwick harmony. care communicate courage collaborate
#testbash @nicolasedgwick need
tester.
#whatkindoftesterareyou
#testbash @nicolasedgwick thanks. Get in touch. Twitter: @nicolasedgwick Slack: nicola (on testers.io or MoT)
As a profession we are constantly striving to move away from the stereotype of QA with success defined as zero bugs in production. Instead we strive for our companies and teams to understand that testing should be considered throughout and within the ideas brainstorming, design review and coding activities rather than purely at the end of the development process when a build becomes available. Then, if a bug is found in released software we aim to look at how that bug escaped detection and improve the team’s testing, coding and design processes going forward.
However, hearing the phrase “there’s a bug in production” still drives a lightning bolt of self-doubt and blame through my very core. I start questioning internally whether I’m being blamed for the failure and kick myself for missing the bug as I feel the adrenaline flow and my heart beat faster. Even in the best agile project team where blame is never mentioned – I still blame myself for letting the bug through, even though logically I know that I did no such thing.
I’m sure I’m not alone.
The truth is that the adrenaline and self-doubt can be great drivers of understanding problems, finding or confirming fixes and staying alert until the situation is resolved. But, when these situations occur on a frequent basis, or in batches without sufficient recovery time then the blame and self-doubt can take hold.
Even in the best projects with collaborative teams experiencing minimal production issues – It can be hard to maintain a healthy and happy sense of self whilst also being the ‘bad guy’ pointing out the problems.
There’s no perfect solution to this situation but I have a few ideas to share, drawn from my own personal experience. Hopefully this talk will inspire other testers to share stories, share experiences and (potentially grudgingly) admit that testers, like their team mates, are human too.
The following resources were mentioned during the presentation or are useful additional information.
Created by Rob Lambert & Software Testing Club
Here’s what was said about this presentation on social media.
for free. You
can too.