Tips for effective communication between Testers and Developers

Most of the testers would have experienced a fair share of tension with fellow developers at some point in time.

Do you have any idea that why is it happening?

How can we get rid of this?

Most of the time, these two tracks are mistakenly perceived as polar opposites. Actually, they are not.Moreover, they are two sides of the same coin.

Having said this, Why not arm yourself with few tips, which are simple but quite effective that ease tension between both the parties?


Let’s begin.

  • Much of the interactions between testers and developers happens through bug reports. Make sure that as testers, we are writing comprehensible bug reports. 
  • Most of the times, We heard programmers complaining that the bug report lacks the necessary steps/ conditions which are needed to reproduce the bug. This kind of reports may eat a lot of their time. Be sure to take extra time to write clear and detailed bug reports with all the necessary information.
  • Some of these bugs are being rejected saying various reasons like “minor”, “unlikely to happen in customers end”, “configuration issue”, “risky to fix because it may affect other parts of the system” etc. Do not take these rejections personally. Instead, try to convince them by adding little more extra details like the potential impact of these bug in the real world. Spend enough time to do pretty good research on these before adding it into your bug reports. 
  •  Pay special attention to your tone in your reporting. Be neutral.I'm right
  • Never underestimate testing as a fault finding mission.If we do this, naturally the reaction that we will be getting is negative. Programmers do care a lot about the work which they are doing.Because of that if someone finds flaws in their work, their natural reaction won’t be positive. Instead, consider testing as an integral part of the development process itself. Same time as a service in order to improve the quality of the product. 
  • Most of the programmers concentrate on the certain module of a particular task. Often they lack the understanding that how it fits in the entire system. In contrast, testers (black box testers) won’t have many details on the individual module. However, they have the big picture of how it fits in the entire system. If we have the basic understanding of these two perspectives, this will considerably reduce the friction.
  • Often QA helps to troubleshoot and spot things which developers won’t think as a major problem, but the customer would.
  • Sometimes there happens to be a conflict in the interpretation of requirements.Such scenario, it is good to have discussion including both the parties with Business Analyst / Customer  in order to get common understanding team work
  • Testers and programmers should work together instead of working against.This happens mostly because they don’t have a clear idea about their goal.The goal should be to ship the best product within the budget and project constraints. Working together also means both development and QA team in the same phase on the project schedule, priority list and requirement changes.
  • Active engagement of both the parties earlier in project life cycle also helps to avoid certain conflicts
  • Try to get the critical requirement clarification and testability details as early as possible. This can be applied to defect reporting also.Don’t wait for the last moment to raise the all the critical defects. This may create unnecessary tension in the team and also leads to missing project deadlines.
  • Practices like Unit Testing and Code reviews before delivering code to test team will ease the job of testers as well.Hence they can test more effectively within the allotted timelines.

In my experience, I’ve found that these tips will go long way to build a successful relationship, mutual respect, and credibility in general.


Your goal should be bigger than your ego

Biz Stone

Feel free to share your opinion.