As I write this, I am less than a week away from giving a testing talk with a difference at HUSTEF 2023 in beautiful Budapest https://hustef.hu/steve_watson on a subject not entirely related to just testing.
Ok, that’s a bit cryptic, but essentially rather than another talk on how you can solve all your problems with automation or learn this technical skill or that technical skill, I’m focusing on something that is very rarely covered at a testing conference – mental health.
As testing professionals, the roles we perform can be stressful. Whether its being a sole tester trying to keep up with half a dozen developers dropping code on you, a newly appointed/promoted test lead/manager trying to get to grips with the role, or a programme test manager trying to co-ordinate multiple workstreams with different stakeholders and teams, its not always easy. But we don’t talk about it!
We are bombarded (yes literally) with ‘how to improve your testing process’ talks, podcasts, blogs, feeds etc – just have a look at LinkedIn for example to see how many opinions are shared about doing testing better/differently/faster. Then look at how many focus on the human element and the effect that working as a tester has on us – hardly anything in the testing space. You have to look outside for that, but my question is why?
So I decided to do something different and share a very personal story from when I first got into test leadership. I was badly burned by the experience, and it took me 6 years to get back into leading afterwards. Years later, as society became more open about mental health and well-being, I kept hearing things that I thought would have really helped me back then, so I have put it into a talk.
Once I have delivered my talk at HUSTEF, I’ll happily share something here, in the hope that a) it gets people talking about struggles, b) some of what I say resonates with people, c) some of what I have learnt will be of practical benefit to others and d) it will spur other testers to start talking at conferences about mental health.
I would like to say a HUGE thank you to the HUSTEF committee for accepting my talk, and shows that they are open to a broader range of topics to benefit testers. I am so grateful for this opportunity to make a difference.
We’ve got more than enough technical talks to last a lifetime – its time to focus on something different. Are you with me?
Steve Watson - Musings of a Test Manager 
Much of the stress testers experience is self-imposed and entirely avoidable, arising from their inability or unwillingness to embrace the infinite nature for testing. There is a pervasive attitude that this infinite task can be completed if you just work a few more late nights and weekends. Of course that’s nonsense, and a good tester will always be able to think of more tests they could do if they had more time.
Perhaps the most liberating thing I’ve heard was someone (Doug Hoffman, I think) 20 years ago saying “There is always sufficient time to test”. The amount of time you spend is always a balance between the cost of the testing you do and risk associated with whatever testing you don’t do. And you can never do it all.
In most cases, the company you work for have (whether they know it or not) chosen that balance point. However much time they give you, that’s what you’ve got. Your only responsibility is to make the best use of that time.
It’s not your responsibility to move the balance point by doing unpaid overtime. If the company wants to move it, they can allocate more time. If they are not willing to do that, they have to accept the resulting risk. If they are not willing to pay more, it means they do not value the additional testing, so why on earth would you do it for free?
I have never allowed my testers to do unpaid overtime. Work 7.5 hours then go home. Or ask if overtime payment has been approved. The only reason for doing unpaid work is if you benefit from it personally by learning or gaining more experience. But that’s your decision, no one else’s, and you must not let them take it for granted.
LikeLike