What is the Best Way to Make Developer and QA Relationship Healthy?

Again, I want to share my experiences with you on an interesting software testing topic. It’s a hot topic in any organization, yes as a tester or QA you can guess it, nothing other than – Testers vs. Developers.

Testers the troublemakers

It’s funny, how almost everywhere developers consider testers as the troublemakers. Actually it’s not their fault, no one like to hear faults in his/her own baby. And same thing which we (tester) are doing, of course intention behind that is to deliver quality output to client. Constantly there is bitterness at some point in the game between these two roles. Wonder why? It’s the genre and responsibility of these two roles.

When bug count increases or bugs are severe and it’s causing difficulty for developer to solve that bug, developer get frustrated at the count and even at the person as well. The understanding level between these two roles conflict not only in one place but in many areas.

So how to make a good and understanding relationship between testers and developers?

My experience says that teamwork and friendship are the best solutions. If you could be a good friend of developer then you can challenge him to issues, and for sure that person take it positively and work better. It’s the responsibility of both to ensure that the ultimate output is to work at its best. While the developers should ensure that there are no bugs out of what they develop. The testers should ensure that if there are bugs, those should be given, handled at the correct time and scope, where completion comes in.

When you are a QA and working with a team for long time, the relationship between you and developers becomes friendlier. As a team you are able to work together finding defects beforehand, which is appreciated always. Not only that, sitting together in a discussion of designs and solutions can make the developers to be aware of the different issues and areas to improve quality, thus taking the quality mind-set a step further.

As a tester, you find the defects but it’s always good to share some tactics with developers on how to test the application.  Maybe, this will help the developers to test better before delivering the product. But this can work only if everyone is co-operative enough to look the final target i.e. “to deliver with quality”.

Let’s share your thoughts:

What do you think is the best way to make developer and QA relationship healthy?

------------

Few of my thoughts on this are:
1. Share your strategy with developers. Don’t keep it in mind thinking that you will mark it as an issue at later stage.

2. Try to build friendly relations with developers, so that they can feel comfortable to share anything with you.

3. Keep your issue reporting style positive, it should not hurt someone’s feelings.

You might be a developer or QA, let’s add your thoughts in this discussion. So that our ultimate aim of “delivering quality output” will be achieved together.

About Author: This is a guest article by ‘Tejaswini patil’. She is working with an E-learning organization as an Associate Manager QA.

Like this article?  You may want to subscribe to Email Newsletter!
Also don’t miss our another interesting read on software testing – Living Life as a Software Tester!



Get FREE eBook + Blog Updates By Email!

Subscribe to get software testing awesome articles and free resources. Enter your email address and click 'SIGN UP NOW' button.


58 comments ↓

#1 Kiran on 07.01.10 at 7:17 pm

best as always.

battle between tester and developer will continue. it should be always in positive directions. don’t take things personally.

what else i can say?
best luck testers!

#2 Bjorn Mikael Wesstrom, PMP on 07.01.10 at 10:06 pm

Great article with which I can only agree completly. Similar conflict problems you find between Project Managers and Test Managers and in my experience the same general tricks works in these cases. Clear and anticipated comunication. Strong friendly relationships and try to be a nice guy. :)

#3 GaneshRam on 07.02.10 at 4:41 am

Addtional to mentioned points:
Whenever they deserved it is good give appreciation words for their work… I personally experienced all developers like this and hav gud relationship with us(testers)

#4 Tejaswini on 07.02.10 at 4:48 am

@ GaneshRam

Great said, yes it’s true.

#5 Partap Sandhu on 07.02.10 at 4:54 am

Friendly relationship with developers is the best way to keep your relationships cool with the Development Team. This can be done by sharing our time and Lunch box in Lunch break . This will help you to make our relationship better with Developers.
Sharing the Test cases some time can harm your incentive parameters so keep both the things in balance and try to improve your relationship instead of sharing our test cases prior to execution!!
There are few more things:
1. Wish good morning to colleagues, when you come to the office.
2. Wish good evening while leaving the office.
3. Don’t forget to send greetings on birthday and marriage anniversary.
4. Appreciate their good work in Interface.
5. Suggest and help the trainee developers to write their code better. This will help you to improve your relationship better in present and future also.

#6 Motiram Patil on 07.02.10 at 4:54 am

Yeh! I am agree to the points mentioned by Tejaswini, However would like to add some points to the above list..

There could be time when clients wants a software to be developed by keeping the end user in mind and developers may develop it accordingly.

In such a scenario, Its developer to explain how a particular functionalities is to be tested and its a QA to understand the needs of the client to test the same in required fashion.

Again, once the bug is raised, developer should first think from QA perspective and then act according instead of directly jumping to the battle if any :o).

It is really important for both to understand the real need of how and where the quality of software should go.

#7 Tejaswini on 07.02.10 at 5:19 am

@ Motiram Patil

Very valid points, both should understand their responsibilities. I know Motiram, and being a developer he posted very positive comment for this article.
Thank you so much.

#8 Dheeraj Mahadik on 07.02.10 at 5:20 am

Good article Tejaswini,

I have read few more articles about developers and testers relationship before. The fact is that the project/product goal should be clear to all team members. If a product is delivered with high quality and within the time line, testers only are not creditable for that; developers and whole team is equally shares the credit.
Basically it’s a learning process, developer learns to write efficient, optimized and quality code; testers learn how, when and what to trace for the bug; and ultimately it becomes the practice for both. So there is no issue of conflicts between each other. But still all this is an ideal scenario.

A healthy relationship between whole team can deliver a good product as team work for a common goal.

#9 Nishant on 07.02.10 at 5:43 am

I think whatever Vijay has suggested is right.

#10 Aman on 07.02.10 at 6:12 am

Thanks Vijay…

#11 adithya on 07.02.10 at 6:21 am

hi everyone,
It was nice to read something which is very common it industry and no one try to share their thoughts on this perspective.Great to have so many comments related to this.I am a QA person as always i give high priority for quality.Regards to the concept,i would like to say that it all depends on team work.IF testers do their job well and developers do their job well,with no doubt quality comes into place at the right time.Its good have a good understanding between two different and very challenging category.I would like to suggest that ,it will be nice to have a debate on the project which they handle ,once in a month,i feel it will be nice and really challenging and everyone will get a chance to raise their voice.cool.Thats about it.Thank you for spending your precious time on reading this.good luck.Last but not the least,Testers,”you just rock”.

#12 Tejaswini on 07.02.10 at 6:41 am

@adithya

Thanks for your views :)

#13 GaneshRam on 07.02.10 at 6:45 am

@ adithya
yeah… you are right. but this article is more concern about overall relationship than project debate relationship or project quality. As u said QA member should be aggressive on them but at same time we have to maintain good relationship apart from meeting room battle. we have to remember, developer also working hard for the project.
@ times, both tester and developer do silly mistakes.

Thanks Tejaswini for ur post.

#14 Santosh Bhaskaran on 07.02.10 at 8:51 am

Hey Tej! Good Article! I agree to what you say, building a good relation within the team is a must, more over one should have a general conversation apart from project. It’s a human tendency not accept negative feedback or review, but if one as a developer takes negative view as positive this will enhance the product development but also his development skills for the next assignment….keep writing such good articles…Hat’s Off!

#15 Viswanathan D on 07.02.10 at 12:13 pm

Hi, Tejaswini, it’s very good article and all well said, as long as we approach the developers in friendly manner and patiently explaining the issues, we can maintain the good relationship with them. We do this way in our team, and we always have good relationship with development team. Thanks for your article. Keep writing more articles like this.
Viswa

#16 Nandan on 07.02.10 at 12:55 pm

Hi All,
In today’s Agile world there is no separate development team and the test team..There is only one team that is Product team.. This team contains number of developers, testers, BAs, Db people etc.,etc..Final goal of the Product team is to deliver the quality product on time and in budget.

Now days to bring the different team together so many companies allowing the members of one team to work in other teams, it not only cross skill the employees but also help to understand the challenges of other team…
SO I think we are all belongs to only one team, that is Product team and our goals is to deliver the quality product and hence make our client happy.

#17 Radhika on 07.02.10 at 12:59 pm

Good topic Tejaswini, I feel it’s also good act to have some kind of best practice incorporated as part of project management process. Having a formal discussion set on board, discuss all aspects of what developer understand and tester understand from client requirements, keeping in mind the actual purpose of “Why client asked this requirement?” .To get the value out of this meet some one should surely break the ice, either it be tester / developer and make other think and speak-out. Reason of having such discussion is making those who are not going friendly with cross teams and not sharing their value added thoughts wrt preventive action; make them involved as part of job. So formally having such process will make them practice this and first successful project release will surely have its impact left. And appreciating the individuals for their insight and reasoning skills is must, as this is default motivating factor irrespective of in which profession one is. What all it takes to make customer delighted, manager/management should think, consider, promote and encourage value added process refinements in team . As in past now also detection act hold more visibility then prevention act, this is one possible cause why individuals are not focusing on teamwork/being friendly to other teams, as all done as part of prevention are always considered unseen efforts. But if management gives proportionate value to both preventive and detections acts, more value added services can be assured for client and even every individual will be left with good feel EOD from their services offered.

#18 Raja on 07.02.10 at 5:05 pm

To add to the topic, one most important thing is that how we put the defect or report the defect in tracker(excel or tool) means the description matters in keeping the developers acceptance with easy. for example : use words like, it would be ideal to have the validation……, we suggest to have the alignments taken care….

It would be ideal to share the logical flows and validations discussed in the presence of dev and testing team along with tech leads.

Keep posted unclear cases in common place and get clarified in common meetings.

#19 Rehan on 07.02.10 at 5:18 pm

Thats a fantastic article Vijay,.Friendly relationship with developers is the best way to keep your relationships cool with the Development Team.

#20 shruti on 07.05.10 at 4:33 pm

Very nice article.
friendly relations in developers and testers can solve many problems.

BTW photo is quite interesting :)

#21 Kishore sharma on 07.06.10 at 11:11 am

Yes, the battle between these two clan is inevitable. But there are other aspects to it.
1. There are people who take it so seriously that next time when his/her module come for test. It becomes challenge for tester to come up with bugs.
2. There are people who instead of working on their work/code comes up with fault in the bug report. test cases, or any mistake that does not fall into development domain.
3. There are people who does not bother at all. They leave it to the tester to find bugs, clarify the requirement to development team, and at times they just don’t bother to listen to what testing team has to say about the bug. Their intention is to let the bug be identified by the client and then I will fix.

These are some of the situations that I have faced during my years of testing careers.

#22 Yogesh on 07.07.10 at 1:39 pm

ohhh

#23 vidyut bapat on 07.14.10 at 11:25 am

Excellent article indeed. the earlier it is realised by both tester and developer that they are on the same side, the better it will be for both. and both will benefit in the process. when i was a product developer, and qa came up with defects or comments, i used to get stubborn and etch for a fight. but now years later, we have become good friends, and i have realised how he has helped me become a good developer.
Congratulations, Tejaswini on this small but very good write up. do write more.
and yes the picture is also good.
Vidyut

#24 elly on 07.14.10 at 2:09 pm

Nice Article Tej.
My few cents
–embrace each other with warm welcome.
–don’t forget to write appreciate word for eachother work.
-last but not least clear and anticipated communication

#25 rahul on 07.15.10 at 11:39 am

i want to test one application which is same as appli itunes.. i want to know some quality test cases scenerios for that application

#26 Madhuri on 07.26.10 at 10:58 am

I am also working with an E-learning organization as an Associate Test engineer. I want some suggestions from Tejaswini patil. Can u pls give me email address of her?

#27 Tejaswini on 07.28.10 at 9:36 am

@ Madhuri

You can write back to me at tejaswini.hedawoo@gmail.com

#28 Dimple on 07.29.10 at 9:18 am

What is/Is there any difference between development and testing environment.

Ex: With same application (AUT) development will find less defects but testing find more defects. what is the cause does the environment impact pls let me know diff b/w dev and testing environment

#29 Tejaswini on 07.29.10 at 9:51 am

@ Dimple

Development and testing environment will always be the same. Yes, it may happen that tester will find more defect and development will less. Coz it’s tester job to find defects and it’s developers job to review his/her work.

#30 Dimple on 07.29.10 at 9:56 am

Tejaswini,

Infact i also answered same as u mentioned by stating only diff would be login credentials from dev to testing…but interviewer was not convinced…no idea if they were looking a specific term/explaination called IDE :-(

#31 Tejaswini on 07.29.10 at 10:00 am

@Dimple
No i don’t think so, if IDE is applicable for developers then it should be for Testers as well.

#32 Dimple on 07.29.10 at 10:49 am

Tejaswini,
Thanks for the info……could be they were expecting something particular stuff that has been followed in their company…:-)

#33 vijay Agasar on 08.08.10 at 4:59 pm

Thanks to Tejeswani and others. Becaus i am fresher and i have no idia about software Testing. But while i saw information about this topic from you, i really happy and its intresting. And i try to become a Software Testing Engineer….Thank you.

#34 swapnil on 08.25.10 at 8:17 am

I wish if there was machine / deivce which could display the metric on processing capabilities of mind.This would
have reveled that mind processing required for architecturing the complex testing environment and writing complex algorithm is the same.So lets not compare.Making imagination to work is for both the people.

DEVQA

#35 Mohamed Shalash on 09.27.10 at 12:45 pm

the best way is to make it friendly but with some type of kindly formality.
testing/QA managers contributes towards the organization strategy.
and i love the challenge way but if it is not controlled it will diverse from required objectives.
and last thing to say it is professionalism in work, understanding of rules and wise management is the best

#36 shakti gupta on 10.08.10 at 9:54 am

You said a software developer can be a tester, but I must say software tester cant be a good software developer. There is no comparison between software tester and developer. Software Tester are nothing before software developer. A developer uses whole of the mind, techniques, effort to write a piece of code to develop a software or application, and what a tester does, just test that and find bugs, if this work is assigned to another developer, he can easily do testing because a developer can be a good tester, but a tester cant be a good developer.

#37 Anuj Sharma on 10.20.10 at 11:02 am

df

#38 Uzair on 11.10.10 at 7:40 am

huh frienshippppp… It reminds me dialogues from Dr. Asthana ( Movie: Munna Bhai M.B.B.S) “If I’m to operate my dughter; my hands will tremble because I love her”.. In the same way if I’m developer’s friend I may have some soft corner for his work in my heart and I may not be aggressive against the work product.
I think instead of friendship we need professionalism. Make developers realize that Quality is the common objective and common responsibility and Testers work to find bugs in work product and not in developer; so it should not be taken personal.

#39 Nahuel on 11.23.10 at 8:53 pm

@shakti gupta totally disagree… a good tester can always be a good developer, a good developer will not be always a good tester, there are certain skills that you can’t learn in a book. You can always read about how to implement a better algorithm but you will never find a book about “where are the bugs”.

#40 Shee on 12.09.10 at 9:26 am

I am the only tester in a team with 3 developers. All it takes to have a good relationship are these:

1. Always judge objectively.
2. Report professionally.
3. Discuss openly.

#41 Goutham on 02.02.11 at 1:13 pm

Awesome!! the comparison between Dev and QA but practically this comparison may not true because the developer and tester both have their respected responsibilities and they are following their standards, the friendly relationship may the causes the exceptions and enemy relationship creates the out of bound so my opinion is there should not be any comparisons between devs and QA that is their duty

and other thing is developer will implements by learning bu the QA will test by thinking….

#42 Madz on 02.08.11 at 10:25 am

I have always been an SQA ever since I started working, and yes developers and QA’s always tend to repel each other. Most developers have positive mindsets whereas we QA people have negative mindset. Oftentimes it’s hard to point out several defects to a developer who is not that open to accept that his work is not defect free, but as long as you communicate it in a friendly, professional manner, try to make it look like you’re doing him a favor or help (because the documented defect won’t reach the client anymore, that’s bigger trouble), always make sure you can backup your statements and provide screenshots, and even videos so that there is always proof.

I think chatting and spending time with developers where the topic is not about work also helps you become a little bit more closer to them. Try to always greet them whenever possible, ocassionally ask for their input or help and praise them when it’s due.

#43 AKS on 02.08.11 at 11:14 am

Good! Good! Keep it up

#44 Joe Keil on 02.10.11 at 8:09 pm

Developer don’t understand the SDLC and complex test cases that’s why they are angry when QA find bugs.

#45 Brijesh Sinha on 04.20.11 at 5:04 pm

A good article……..i have very good relation with developers………We always appreciates each others work and helping to understand or describe the problem. The best example is that we are indulge in buddy testing.

Thanks!

#46 Taahaa on 04.26.11 at 2:04 pm

The way the tester need to approach with the developer is important….. ya its a nice article..

#47 Great tester on 05.03.11 at 12:23 pm

Waste article

#48 SaP on 05.16.11 at 11:16 am

For all Testers:

The best tester isn’t the one who finds the most bugs or embarrasses the most developers. The best tester is the one who gets THE RIGHT(not most) bugs fixed.

#49 PANKAJ KUMAR MAURYA on 05.21.11 at 7:49 am

Hi All
Realy nice article

#50 Mani Chander on 07.12.11 at 8:16 am

yes, it is fruitful idea.
after all we are the friends right?

#51 Deepak Prasad on 12.21.11 at 5:33 pm

Hi All,
What I said about relationship of Tester and Developer, I am working as a Tester since 3.4 Years but I know how to make work from developer cause Tester always find fault in developer work and nobody wanna bad stuff in his/her own baby. So I would suggest to all Tester be make fruitful relation to developer.

Thanks

#52 anu on 02.09.12 at 7:54 pm

i want to ask a doubt please …..how about (mainframe testing and mainframe admin )……….and how about software testing …..plz give me the correct differences. AS a fresher I m really confused to choose my career i have completed mainframe admin but no hope for openings now and I have decided to start my career as tester …….but only one doubt is ….after 2 year will it be possible for me to shift my career from normal testing to (mainframe either admin or appl .).or else to developer .in any field ..since I m really interested in mainframe i ask this question ……..plz help me out …im really confused and also I m making u people to get confused i suppose :-P…..and what shld i chose ….regarding the salary package ..etc etc

#53 Shagy on 04.26.12 at 7:32 am

Actually, we in our org follows the same strategy, making friendship is the very good way for handling the developers. Also If we QA guys tell the in very quiet mode, then he/she will understand it soon..

-Shagy

#54 Ritesh Chandawar on 10.02.12 at 6:03 am

I haven’t read all comments so some one must have covered it, but I want to make some points here.

As everyone said Testers are always rival of Developers…. is it true, as long as you will point out their (developers) faults in form of Bug, Defect, Issue and whatever u call, they will think that you are their enemy.

But if you know how to present your issue in front of them then you can solve many problem their itself.

So how to do that? (It my or you can say RC’s technique)
Always present your defect in term of inconsistency in the workflow as a user point of view and not as a defect.

Rather than saying this is defect, say if user will do this then he will get this so do you think this is right?
After this he him self will say no this is a defect please log it. (Tht’s it your job is done.)

Another Scenario:
Rather than filing defect in a system if you are seating close to developer always say that it is very hectic to log a defect in system and track it, it will consume both of our time so can you please try to fix it if possible. Most of the time developers will agree to this kind of situation because they also don’t want more defects against their own developed area.

Please try these technique and let me know if those are working for you.

ritesh.chandawar@gmail.com\

Ritesh Chandwar
SSQA

#55 Ivan on 11.30.12 at 6:38 am

@Ritesh Chandawar
Your second scenario is not permitted, as I know in many companies. When testers got faults, they should log it somewhere, like in VSTS, so that the manager can trace the advancement of given faults.

#56 Vipin on 04.10.13 at 6:31 am

Bullcrap! Testing is so boring and too small of an activity to be a job. you just have to use and find defects in software that programmers create. There is nothing new you’d be using same tool all the time be it QTP etc. No use of technology & no power to create.

#57 Belinda Blok (@BelBlok) on 08.20.13 at 1:16 am

Create the environment where the collaboration is carried our with mutual professional respect, no private agendas, and the ties are developed. To testers, do your homework, don’t just flag things because you don’t understand the functionality. To the developers, when your QA asks for time/meeting, make it happen; a tester seeking answers is a bug resolved before it happened.

I can see same pattern in UAT participants and tech team…it doesn’t have to hostile if both are working with a sense of cooperation and open communication.

#58 Priya on 01.28.14 at 12:21 pm

:)