Do not expect everyone to understand testing!

As a tester, it is your job to tell others what you need in order to do your job properly. A tester is largely affected by the choices made by management and programmers. If other stakeholders are unclear about their plans or design a product which is hard to test, then this will affect your test plan. I’ts not that they do not understand or care about testing and software quality. They probably just do not understand what impact their actions can have on the test process. An important part of testing is to explain testing to other stakeholders.

I read somewhere that your explanations about testing are like a flu vaccine, healthy and not painful, but the effect wears off, so you have to do it over and over again.

Never dream or wish to have absolute control over the release of a product.

When testers control a release, they must also bear full responsibility of the quality of a product. What I have seen happen is that if any bugs are missed by the testers and make their way to production, the rest of the team (in most cases) will blame the testers. Why did the tester release such a buggy product? On the other hand, if a tester delays the release then they will come under pressure for being perfectionists or quality fanatics.

The people who control the project are the best suited to hold the responsibility to release the product.  So if you are ever given the authority to control a release, insist on sharing that authority with others in the team.