How should testing be organized?

Question

Software testing

Hello,
I was interested in the topic of testing, but there is nothing structured on the Internet.
I'm interested in how testing works in companies.
It is not clear what should follow.
In my understanding, this is as follows:
1) Documentation is released, it is analyzed.
2) On the basis of paragraph 1, test cases are compiled.
3) They write real code based on test cases (or maybe they don’t, judging by the articles on testing, which are more like articles about management).
And one more thing: what techniques do testers usually use?
After reading books and articles, I have the feeling that they themselves do not know what they will do, but it is important for them that they are hired, where they will actually be shown what they need to do.

Answer 1

How is the testing process most often arranged in small / medium product companies:
1. The feature is being sawn by developers.
2. Is sent for peer review.
3. After the review, the tester comes and runs the feature branch using his test cases. Most often, this is a smoke test and the compliance of the feature with the necessary requirements. If this is some kind of big / global feature, then regression testing is already going into battle here.
In general, the processes are different in all companies, it really can be the development of TDD, which you described, or maybe the tester sits and comes up with test cases in his head and they are somewhere in his notebook.
Therefore, in part, the feeling of misunderstanding of one's task is even appropriate in this case at the initial stage.