Tester Must Need Four Basic Good Communications With The Development Teammates

Tester Must Need Four Basic Good Communications With The Development Teammates

Tester must need four basic good communications with the development teammates. Good communicators know how to explain the test results, even negative results such as serious defects and quality risks, without coming across as preachy, scolding or defeatist.

- The first one is, the tester must think of your colleagues as teammates not as opponents (or) enemies. The way you think about the people on that the way you react to them. If you think your colleagues as teammates, then you use polite and tactful communication. But, if you think your colleagues as opponents (or) enemies then you start criticizing them. It means, you need not to think too much, like in terms of kinship (or) achieving world piece like that. Then you might get a confusion like what should I kept in my mind? - You should always keep in mind that everyone in the project must act like a team player, ours common goal (or) motivation is delivering a quality system, for that we must work together to accomplish that.

- The second one is, tester must recognize that your colleagues have pride in their work, just as you do. So tester owes them a tactful communication about defects you have found on their developed system. If you find the potentially embarrassing findings, you shouldn't use harder communication on your findings, if that is valid to. You must in a neutral, fact-focused way. You should avoid criticizing people and their work products, if they did a mistake so. Instead keep your written and verbal communications objectives and factual. You also avoid a lot of unnecessary conflict and drama with your colleagues.

- The third one is, before tester communicate these potentially embarrassing findings, mentally put yourself in the position of the person who created the work product. How are they going to feel about this information? How might they react? What can you do to help them get essential message that they need to receive without provoking a negative emotional reaction from them?

- Finally, keep in mind the psychological element of cognitive dissonance. Cognitive dissonance is a defect – or perhaps a feature – in the human brain that makes it difficult to process unexpected information especially bad news. For example, you want to stop yours friend smoking habit. Then you said that stop smoking, I don’t like the smoking. The friend who has the regular smoking habit, he think like why am going to stop smoking because of he’s not like that. So, at the end there is creating conflict between friends. Instead of, you just change your way of conveying your suggestion like polite and factual manner like Hey, friend you are really good person and kind guy, a lovable husband and a great father to your children you have lots of good habit. But you smoke regularly those spoiling your good habit and mainly, your health.  Because, of this statement your friend try to change this behaviour slowly. So, while you might have been clear in what you said or wrote, the person on the receiving end might not have clearly understood. So, before assuming the worst about someone and their motivations, instead confirm that the other person has understood what you have said and vice versa.


要查看或添加评论,请登录

Karthikeyan Rajendran的更多文章

  • Why interfaces are used in test automation frameworks?

    Why interfaces are used in test automation frameworks?

    Back Story: One day at the cafeteria, a colleague and I casually discussed the framework we designed. He raised a…

    2 条评论
  • Automate RESTful API using RestAssured - {Basics #2}

    Automate RESTful API using RestAssured - {Basics #2}

    Hallo Amigos, Welcome back! First of all, thank you for your support, comments, and encouragement, which boosted me and…

    9 条评论
  • Automate RESTful API using RestAssured - {Basics #1}

    Automate RESTful API using RestAssured - {Basics #1}

    Hallo Amigos, This is my first step in the new year 2023. I would like to share my knowledge in the QA/testing world.

    11 条评论
  • Basics of Security Testing

    Basics of Security Testing

    Hi Friends, Today, I took a wonderful session on the topic of "Basics of Security Testing". I have shared a great chunk…

    3 条评论
  • How do you describe Scrum?

    How do you describe Scrum?

    #Agile #Scrum While last week is was getting one post from linked In group. Which was, “What’s the best way to describe…

    8 条评论
  • Do's and Don'ts For a Tester

    Do's and Don'ts For a Tester

    Hi Friends, Today, I took a wonderful session on the topic of "Do's and Don'ts For a Tester". From my experience and…

    2 条评论
  • How many (what percentage of) test cases do you automate?

    How many (what percentage of) test cases do you automate?

    “How many (what percentage of) test cases do you automate?”. It is a quite common question raised from the managers.

  • Selenium IDE Firefox add-on end of life!!!

    Selenium IDE Firefox add-on end of life!!!

    The Selenium IDE add-on for Firefox, an add-on used to automate tests in Firefox for web development and other testing…

    2 条评论
  • The race between Automation Testing(Rabbit) and Manual Testing(Tortoise)

    The race between Automation Testing(Rabbit) and Manual Testing(Tortoise)

    Shall we start the race between Manual Testing and Automation Testing……………… Oh! Yaaaaaaaaaaa…………………. One,,,,,,,,,,,,…

  • A/B Testing Certification

    A/B Testing Certification

    In current trends, data involves a product, service, or content in the each and every page of a website holds valuable…

社区洞察

其他会员也浏览了