How many iterations of testing one task are considered normal?

Question

Project management

The fact is that the tasks go through 5 iterations of testing and I don’t understand whether this is normal or not. After the first iteration, we get a list of bugs that need to be fixed, fix it, send it to the second iteration and get a new list of bugs, everything is fine with the old ones, fix it, send it to the third iteration of testing, get new bugs again, everything is ok with the old ones, fix it, send it for the fourth/fifth iteration and only after that we close the task.
New bugs in each iteration are almost never connected, but obviously we lose time on these wanderings back and forth.
I would like to hear opinions, how many iterations of testing are considered normal? Two? Three?
And how is it in your companies?

Answer 1

As much as you need, even until blue in the face. The developer should also test and try to prevent this from happening.

Answer 2

Try to agree on an acceptance testing plan before starting development and have the developer do the first trip. Is there a hurry (the developer is trying to quickly turn off the task for the tester at the expense of quality) tmguru.ru/baza-znanij/protsess-testirovaniya/plani...

Answer 3

Until the finished code works as written in the TOR and does not break the existing code