How to properly present yourself in a team and not get toxic

It would seem that why pick up the words to report a bug to the developer? Walked up, said what he did wrong and reminded him how many times a week the situation has been repeated, and, in general, the guys from N company were doing the things differently a long time ago. The more arguments and facts that point to the fact that the developer is NOT right, and you are right, the fewer complaints about your work, right?

But here's the thing: such unipolar approach usually leads to finding a "witch" and, as a consequence, replacing you with another, more team tester. And when you're hired you're told - it's important to be competent and meticulous! And when it comes to business, it turns out that no one wants the honest approach, and that "their guys" win. So what is the truth?

In this talk, I will tell you how this happens and how to achieve team success by doing your job efficiently.