Tester Must Need Four Basic Good Communications With The Development Teammates
Karthikeyan Rajendran
Selenium 3&4 | Spring Boot | Playwright | Cypress | Postman | RestAssured | Supertest | Restful API | GraphQL | Contract Testing | Micro-service | Gatling | K6 | Locust | JMeter | Performance Engineering | SQL
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.