Challenges in Tester’s daily life

what are some of the challenges you face in your day-to-day life as a tester?

Share your experiences and strategies for overcoming these obstacles.

1 Like

quote=“ansha_batra, post:1, topic:77230”]
what are some of the challenges you face in your day-to-day life as a tester?

Convincing people that security is not “optional” :sweat_smile: :sob:

It’s mainly due to them not understanding what security is and what the threats an be. Even after explaining the impact of a 9.8 CVSS scored Remote Code Execution, it landed on the backlog. Ahum… backlog? I had to explain to hotfix this asap. It still took them 3 weeks to do it.

So yea the challenge I face is that people have no clue about security and the impact even after explaining it.


Shifting the mindset of people who have worked in the field for years and always had manual testers test all their requirements (aka. had safety nets) to the mindset that manual testers job is not to be your safety net, but help you do more specialised testing (e.g. performance, security, accessibility, help you with test cases, …) and you yourself should be your own safety net.

How we are doing it? One small step at a time. We started with pair-testing sessions after every task, to raise the confidence level of the developers that they can actually test their own requirements.


The main challenges that I have is that quite often as another user mentioned we are seen as the ‘safety net’ and perhaps this means that the work can be sub-standard.

Also as I work for an agency my time is paid for by our clients and everything has an estimate. If a piece of work has a lot of bugs in it then more time is needed for a second or third round of testing but this has a knock on effect otother projects that I am booked on.


Thank you for sharing your experience! It’s indeed a significant challenge to get everyone on board with the importance of security. Your story highlights a common issue many testers face – the struggle to prioritize security amidst other pressing tasks.

One strategy that might help is to provide real-world examples of security breaches and their consequences. Sometimes, concrete cases can make the risks more tangible for stakeholders. Additionally, collaborating with your team to create a risk assessment matrix can illustrate the potential impact of vulnerabilities in a more structured way.

1 Like

I completely understand the challenges you’re facing, especially being seen as the ‘safety net’ and dealing with tight client deadlines. These issues are quite common in our field.

To manage the perception of being a safety net, I’ve found that fostering a culture of quality within the team helps. Encouraging developers to take ownership of their code and promoting practices like pair programming and code reviews can improve the overall quality of work before it even reaches the testing phase.

Regarding the time constraints, one strategy I use is to set clear expectations with clients from the beginning.

Thanks for the response!


Not doing much testing in the past few years. And as time passes, and I change jobs and I check with others in interviews I see more companies that want even less testing when hiring for a tester position. And I miss it.

1 Like

1 Like

The biggest challenge for me has been when developers (incl CTO) think they know more about testing than the alleged testing expert on the team.

Resistance to change is always more important than improvements which will elevate quality.

1 Like

I would concur on this.

Sometimes, testing gets dictated by non-testers.

Sometimes, testing gets dictated by so-called “best practices” from some random company which has no relation to what we do or build

Sometimes, testing gets dictated by the wishes of the customers who do not understand the true essence of it. I have seen silly requests from customers because they want to please their management. Crazy loop.

Sometimes, testing gets dictated by the “I want to learn this tool, so let me implement it here” of a colleague/team mate.

As a tester, being aware of what’s going on around is very important. There are too many noise sources out there that can create a problem for testing / testers.

I am against the notion of “best practice”, because it implies that things cannot improve. “Good practice” is my preference :slightly_smiling_face:

Would an expert developer be nudged aside by people that knew nothing about development? Or is it just testers?

1 Like