How should an engineer feel when an issue is found in software ?

When I started my career as a QA engineer I use to get delighted after getting an issue in software. Still I see some of my friends working across the industry as a QA engineer feels happy after finding defects/bugs.  

 I was just rethinking on the same line “What should really be the approach of QA?” Should a QA regret if a bug is found after coding of software is done?

Gone are those days when QA use to gets appreciation based on the number of defects/bugs that are found during the testing phase of a software. I feel the ideal approach of a QA engineer should be more towards preventing bugs than finding them once coding lifecycle gets completed.

How can that be done?

Once requirement gathering is done Developer and QA can pair up and discuss their understanding in order to make sure they are on the same page. Once developer starts thinking about the implementation approach or architecture QA can meanwhile do brainstorming and come up with high level all possible Test scenarios and Test Cases. Once we have high-level scenarios/Test cases ready we can pair up with the developer and discuss it with them, this will help developers to rethink on the development approach or in incorporating all possible scenarios while coding.

As we know the early we can prevent/identify defects least cost a team would have to bear compared to one that is identified later during the development cycle. As a result, it will help in shipping quality product in minimal time.

So let's walk together and change our approach towards verification which will eventually help our client to save huge cost, which again can be utilized for other activities like Technical Debt, Automation, etc..

In fact, I disagree with SDLC diagram given in Wikipedia (source of file is Wikimedia Commons) which is given below, testing should be started from very first day. My definition of testing is not limited to execution of test cases but it involves all QA activity starting from the very first phase of SDLC.

Testing & Development of software in parallel will deliver the best result.

Bringing it up altogether

Delivering a quality product is not only responsibility of a QA but it’s a responsibility of the entire team, it cannot be achieved in minimal time with a mindset of #AchievementAfterFindingBug. In fact, I will encourage to take a #Guilt approach, wherein after finding an issue we should retrospect on our scenario thinking approach of QA.

Let’s walk together & embrace the mantra “PreventingIssueRatherThanFinding” this will help us as a consultant to deliver Quality software at minimum cost.

Please share your thoughts in the comment section, we can connect and talk more. If you enjoyed this post, I’d be very grateful if you’d help it spread it to your connections on LinkedIn or other channels.

Thank you!