Someone interviewed me today on tips for aspiring Software Testers, who are just about to enter the field, and they asked me “What are the challenges today in Software Testing?” It has always been on my mind, and I had talked about it in a recent talk also – for me it’s the Software Requirements. Already there are studies that show that 65% of the defects are attributed to the requirements phase. Add the complexities that are introduced because of the ‘frequently changing requirements’ model of Software Development today, and you got a big problem in your hands.
Someone tried to put the blame on the automation test scripts for the bad quality of the product in LinkedIn, and I immediately asked them, “Have you done thorough analysis at the requirement phase to avoid defects?” I know they wouldn’t have. The team always take shortcuts to develop and deliver faster to the customers, overlooking the various aspects like performance, security, UI, error handling, etc. So, the defects injected because of that are not going to go away, they are going to feed back right into the next development planning straight from the production of the previous deployment. So, it’s wise to address the requirements when they are collected and analyzed.
I am in the process of making videos for my YouTube channel on requirements. You can find some requirements-related videos in my channel right now at:
There are awesome videos coming up on requirements as I talk to industry experts and practitioners on the day-to-day challenges that they face and how they handle them.
So, stay tuned by SUBSCRIBING to my channel here :
If you would like to speak to me about better ways of coming up with Software Requirements, feel free to setup a consultation with me.