How can a tester criticize and maintain a good relationship with the team?
I will share my experience – how can a tester criticize and maintain good relations with the team.
Your criticism should not be taken with hostility. You have to work with the team for several years, go to a barchik with them and somehow build a career.
The tester is the critic
When you are an authoritative critic, your opinion is listened to. Hogwarts Legacy is out – let’s wait for what the critics say before buying the game.
When you work as a tester, you have to criticize: here is a bug, and here the authorization does not work, and here the pen returned 500, and here the documentation is outdated, but there are no logs in kibana, and here the test environment is not available.
If you start a lot of bugs, consider criticizing the developer. Not enough – they can say that you are not an effective QA.
How to criticize and maintain good relations with the team?
1. Start writing
Read Ilyakhov’s books. Try to write about your useful experience in the sandbox T-Zh. Formulate a technical question well on Stackoverflow.
This will give you the skill to systematically and structurally convey your thoughts to another person in text and describe the problem normally in a bug report.
2. Develop critical thinking
Ask yourself the question – “why so?”. Don’t take everything for granted. Critical thinking well develops a broad outlook: travel and work experience on several projects.
With developed critical thinking, you will be able to argue your position well.
3. Turn off emotions
The user, when he could not make a money transfer (caught a bug).
Can be rude to support – you a#y#whether there!
There is no need to convey these emotions to the developer in a bug report.
Write to the point: [crit][prod] Transfers to non-resident accounts do not work.
Affected 60% of users.
4. Learn to express your opinion
Read the article on Habr or VC.
If you do not agree with the author, try to write your criticism in the comments so that it is constructive.
5. Understand the basics of good interfaces
Read Lebedev’s Handbook to criticize UX solutions and objectively argue your opinion.
6. Learn into processes
Once again, I got a task without a description – do not criticize. Get the task template itself and ask the project to use it.
On planning, developers forget to take bugs into work – do not criticize. Create a bot that will send the top most critical bugs to slack once a week.
And read Toverovsky’s book on project management.
7. Praise first, criticize later
Over time, you notice that when a developer shows you the developments on the site, your first reaction is: “look, the button in the footer has moved down.”
Are you sure that by doing so you help the developer. But what is expected of you at this moment is not criticism. Check out his work – wow! I like!” And then tell us about the bugs you found – structured, but not offensive.
PS1 The post was inspired by one of the many comments from @lxsmkv
PS2 I created a project Junes — where novice testers will test your website, bot or no-code solution for free. If you have something to test – write 🙂