What are the types of software testers..?

This question is not yet asking by the interviewer yet., of course this is not an important question my dear software testing freshers., you no need to search Google to find answer for it.., :)
Am not having much experience in Software testing field, but in the couple of years, i come across numerable & memorable testers in the field.
Those guys make some important foot print in my way., I learned some good things which i have to follow., and some ones make me aware about certain things which i should not to do., I can easily differentiate those peoples in categories, Teasers and Taster, Testers.
Let me explain this category from last to first like stack: First of all, i would like to mentioned peoples comes under this 3 category are good at their testing work(Yes, good at their work in their views, In my point of view A Good Tester is the one who make the customer smile).
3) Teaser:
While he got the bug, one he started to laugh and celebrate otherwise, he got frustrate and started to fight with development team., Some times, people in this category is soft hearted means, they just started to cry, "Oh, My God dev team is not fixing my bugs'. like this.., :( They wont take any step to make the bug get fixed., Their full time work may be to glorify the application or otherwise to speck ill about the application., )
2) Taster:
They are test and find bugs and taste it., The bugs exists in the application make side effect in him(got Head ache, BP get high/low, tension., etc). but unfortunately these side effects not bothered the development team., :( They are really worry about the quality of the product., but they show their worries in word not in work.,
1)Tester:
The bugs which found the person make no reaction, she doenst waste her time to think like the silly ways, immediately show faults and clarifications exists in the application to the dev team to make the fixes immediately., she worry about the quality and fear about the failure and transfer the same worry to management and development for to get some good things to happen.

What a tester want?

As a tester i don know how many of you face this question., But in my experience i just expect every time this question from development team. But development team come to me with the answer not with question. the answer might be the project url, some documents or a KT.
As a tester i thought, i have a privilege to ask question about the anything what i do. but why the questions of mine always lead to the critical path.? :)
As a tester, in the testing community we all speck about plenty of testing methodologies, ideas, automation bla bla bla.., but what is actually happens in the organization, in to the team..? Is there any simplest way to apply the methodology recently i learn in the team? I can say loudly "NO"..., then As a tester, why do i still learn every day the new thing come today..?
As a tester i have a hope, flexible, and can able to test the thing what ever it may be., can able to give report.
As a tester, yes my questions some times make my team in to the dark path. But never go to stop this work of asking questions.. Because As a tester, i believe Faith cometh from Hearing, this is the one important quality of tester.Most of the time i wouldn't get answer for every question which i raise. But As a tester i never loose hope.Patient is the power of the tester who want to survive this industry.