Why do testers need test comments?

Question

Agile

At work, a question arose about what I wrote in the cap. They require me to write in the comments to the task, as I understand what and how it is possible to test. Am I the only one who thinks this is crazy??? And, as it were, the description of the task is already in the same jira, and in confluence, so that, in general, I and anyone else can functionally test it. But should comments, for example, intended for a bug tester or a pen tester, even exist? Roughly speaking, it's about the fact that I, as a developer, should imagine all possible situations of non-standard use of what I wrote and tell the testers about it. How true is this?
PS: There is no need for comments like "well, we have it like this", "and we have it like this". I am not very strong in Scrum and Agile and how they relate to testing. Therefore, I ask a question on the topic of how it should be, and not like someone there in another office that has "10 years on the market")

Answer 1

Working for several years as a tester, I came up with a rule for myself:
Everything is very similar to programming: you write code, give names to variables, methods, classes. You think logically and clearly, but after a year: Who wrote all this? What was I smoking at the time? Yes, it happens! ;) We are developing, we have a new experience. New ideas. Seeing old thoughts, we can be horrified)))
In testing, we also do not sit still. We learn and our skills develop. By writing only the title, you may find yourself in a situation that you cannot understand: What do you need to double-check then? I note that the tasks differ in priorities and it may turn out that you will see the task created now only after half a year or a year.
Compare the two headers:
1. Error in the log when downloading the backup
It's clear? It seems to be yes and everything is logical at first glance. The title forces you to go to a specific place in the code: the backup download class.
But here questions arise:
1. What is the bitness of the program?
2. After what did the error appear? Immediately after the start of the download, or did the computer go to bed after waking up?
3. Is it only on Windows 10 or also on Windows 8.1? And how does it behave on Windows server 2012?
4. Are these errors in the log? What if the power cord is unplugged?
The purpose of the comment is to narrow down the problem to such a size that it is clear where exactly to look.

Answer 2

For the tester, some aspects of the implementation may not be obvious, because the black box, for example, the new functionality is implicitly tied to something else. If there is a non-standard case and the developer sees it, then why not save the team time and fix the idea.
well, when the developer and the tester understand that they are in the same boat, then the developer, for his own safety net, will draw the tester's attention to cases that are worth paying attention to.
A pure test analyst in companies is just as common as a unicorn.
All normal testers do this. What is the point of a tester who is unable to create cases according to the requirements?