software testing is tough

Software Testing is Tough

Reading Time 3 minutes

It’s long, it’s hard but it’s worth it

Software testing is tough. Software Testers find bugs, write tests, firefight issues, teach, are expected to learn quickly and as a result it can become a difficult experience.

A Software Tester can constantly face many hardships, let’s have a look at some of them.

Hardships of a Tester

On a day-to-day basis, here are some of the key struggles that a Tester may face:

Testers VS Developers

At times, it may feel like a Tester is constantly having to stand their ground, make their point and convince Developers about bugs and non-functional issues.

Firstly of all let’s make one clear point. Testers and Developers are important for different things. The real benefits comes from the synergy of both roles.

Sadly, this silly thought of Testes VS Developers is simply unhealthy. This sort of thinking breeds segregation and isolation. Therefore, this helps to encourage a very ‘blame’ and ‘fault’ culture.

Unfortunately I have been exposed to this, most noticeably in a Waterfall environment. In a Waterfall environment, since the whole development is done in stages, there is little to no day-to-day interaction between Developers and Testers. This can lead to a very us vs them mentality.

Fortunately, Agile completely promotes a mixture of Developers and Testers therefore somewhat mitigating the idea behind Testers VS Developers. In an Agile environment, Testers VS Developers becomes Testers AND Developers.

Regression: The Silver Bullet

What is Regression?

For starters, it is not there to ensure that an application is bug proof. Regression means one single and simple thing; is everything still working, has a new issue been introduced. Sadly, not everyone understands this.

In some instances, Regression is seen as the ‘Application God Process’ which will catch-all the bugs, find all the holes, makes everyone super happy.

What do I mean by this?

Simply put, a misunderstanding in Regression stems from people, not the process.

In an ideal world, Regression should not be a laborious, long or a difficult task. It should be quick, painless and swift. People on the other hand have a magical gift to turn Regression into a nightmare.

On a whim’s notice, Testers are asked to consider new browsers, new devices, add a hundred more test scenarios, consider extra testing to cover for other teams etc. It feels like people forget how draining Regression can be.

Performing Regression is an important aspect of a Testers life. However, I have seen (first hand) how difficult it can be when last-minute requirements, favors and the need to test everything makes things difficult.

Proxy PO and BA

Overtime time, since Testers go through the application more times than ‘failure of unstable UI tests’, Testers become domain knowledge experts.

Initially, a Tester mostly needs to work with Developers (and other Testers) to test an application and ensure that it works. Overtime the role can become more challenging.

It becomes more and more difficult to devote time towards actual testing. Instead you may find yourself in meetings, talking about plans, strategies and much more. On the surface this is a great thing. This gives the ability to influence decisions, technology and perhaps a promotion.

Hence this drags the Tester away from their actual work i.e. to test.

Software Testing is Tough! Well, Is It?

Most noteworthy yes, Software Testing is tough. Seems like Testers are team players, how could Testers not be?

Developers, Testers, PO, BA all need to work together to convert a well thought plan into a delivered product. If the processes are taken care of, the team will be happy.

Testers are part of the backbone of any software development team and should be treasured.


I am a passionate tester, father, husband and gamer. I love to write blogs about Software Testing and generally contribute back to the Software Testing world.

More Posts - Twitter - Facebook

Published by


I am a passionate tester, father, husband and gamer. I love to write blogs about Software Testing and generally contribute back to the Software Testing world.

  • from my experience, I’ve worked in two different application development companies, it’s very driven by the team and the manager. If it’s a small team then I totally agree too much time is given up to stand ups and meetings to actually get anything done. Larger teams however work well, given the right net of communications. Nicely summed up.

    • Mo

      Hi Frandobagel,

      Many thanks for your comment.

      Your spot on, to much time is taken in meetings and stand-ups. Worse even so when there are no actions as a result of the meetings.

      The trick is to find a balance between work that needs to be done and work which needs to be planed.

      If your interested in Stand-ups, make sure you checkout my blog post on stand-ups here at

      Many thanks for commenting.


  • A bit technical for me but my husband enjoyed it! Thanks for sharing

    • Mo

      Hi Elegant,

      My blog is designed to be a little on the techy side but I do express my views on processes also which may be something which you might find enjoyable to read.

      You should totally ask your husband to checkout some of my other posts.

      Can I ask what field your husband is in?



  • Interesting article- in my job as a financial analyst I am also often the one testing the changes made to our BI system. Because I am a person with a certain technical understanding but no education in IT it is often even hard to find the words that the developer understands.

    • Mo

      Hey Sabrina,

      Many thanks for your comment.

      As a technical geek, I do understand what you mean. I have had to learn overtime how to express myself to different people who understand different levels of language.

      This said, it is an interesting challenge to be able to express the same problem in different ways.

      Many thanks,


  • Jayanth

    Nice comparison between Dev and QA.

    • Mo

      Hi Jayanth,

      Thanks for reading and commenting.

      Can I ask what professional capacity you work in? I ask because I want to gauge a little more about my blog readers.



      • Jayanth

        I am Quality Engineer

        • Mo

          As am I šŸ˜€

          It would be great if you could stick around and checkout some of my other posts since most of them are based on Quality.