This is a good summary. It heavily depends on the people. The testers as well as the devs. And also the org.
I agree on all advantages mentioned by @kinofrost
@jean-l While I see some risk that it can happen what you mentioned I see also problems with not being in the team.
Especial at automation I perceive many testers overdoing it, too much and with a lack of skills.
Developers can at least help to make that automation code better, teaching you how to develop.
And together you maybe come up with new ways of (semi-)automation you have not thought about. Happend to me.
How does this come? What are your experiences?
What was the bad influence?
I find my decisions about testing to be more well informed while being in a team. Because I have more information, context, better insight into the release schedule, shorter feedback loops, good relations to developers …
The only superior I accept is the project manager. My work is to inform him about the state of the product (reporting bugs is part of that).
If they think I should test something different, that the priorities and risks are different than I think, I accept that. I ask for that. No matter if I’m in the team or not.
I exchange with devs, they are a helpful source and often I decide on what to test based on what they said.
But if they want me to (not) test something, they have to convince me. They can not overrule me by force.
With all respect & I hope this can work as guide for you 