The definition and root causes of Fear-Driven Testing (FDT). Symptoms and impacts of FDT on software development and team dynamics. Strategies to identify and address FDT in your projects. Best practices to foster collaboration and continuous testing in your team.
After reading the article, we’d love to know:
Have you experienced Fear-Driven Testing in your projects? How did it impact your team and project outcomes?
What strategies will you implement to move away from FDT?
I had and might still have fears which are related to my personality mostly.
Fear of conflict: I don’t do well in debates and avoid conflict with people. So this makes it harder to assert something I say. I try small things over a longer period which can lead to at least a middle ground.
Fear of letting down myself or someone else: In an environment where mistakes aren’t easily permitted I stay tense and go over my work or check things with people or resources a few times.
Fear of degrading my image: it’s hard to build an image as a great tester in a workplace. I feel it’s way easier to destroy it with a few actions. So I think things over multiple times, maybe write them down without sharing, and I say them out loud to a friendlier colleague. Sometimes it might not make sense so let it go.
Fear of getting fired: not agreeing with the management when they believe you shouldn’t have a word in it is hard to work around with. Sometimes they’ll provide the testing strategy, tools, and estimations without having any idea about the development, risks, or approach. So I end up either disobeying or doing hidden work.
Fear of inferiority: I get intimidated and shy around other organization members who are experts in their field whenever I have to work with them; I feel like I know so little and I might have a wrong perspective on things.
Fear of not serving the right person(e.g. clients): In some companies, the business is driven by people with their eyes on Excel sheets and PowerPoint. So advocating for clients can be tough. I’ve done a lot of ‘hidden’ work with several colleagues once to improve product quality.
These examples just appeared while writing the reply, there are several more I could easily add.
Fear drives the development of several skills, and I believe a balance of fear and courage is necessary to excel.
This is an interesting read.
I have definitely been subject to FDT earlier in my career. The biggest impact i think was on my mental health as I would do many a late night doing extra testing and then still not being satisfied with my work.
The main road out of it was my experiences I gained in my journey from working at different companies. Seeing the different development teams at work and contributing to different testing practises gave me a lot of insight to all the environmental factors that can impact the quality of a product.
Being aware of these factors allows you to make them known to all the stakeholders and it also gives you a chance to influence them as well as manage expectations (including your own).
The definition and root causes of Fear-Driven Testing (FDT).