Listed below are the few types of QA you find in any organization.
Extra active QA
100% active while testing. These kinda QA's would exactly know where, why, when and how the application would crash.
Perspective QA
- Always things about how an end-user would use the application.
Quick QA
- This QA just tests certain main features and gets the build approved.
Verbal QA
- Tests the application and sits with the developer and discusses defects verbally and doesn't log it in the tracker.
High-per active QA
- Doesn't take breaks and always concentrates on breaking the code.
Social QA
- Always socializes with other QA and tries to gain knowledge from other QAs.
Abusive QA
- Doesn't like the product he is testing and always cribs about why he opted testing c.
Lazy QA
- Tests with zero enthusiasm. Run the application for 10 mins and gets involved with some other work.
Semi Active QA
- These kinda QA are good at testing but would be active in certain intervals of time.
Developer's boy QA
- This kind of QA's always inform about the bug to the developer and asks him if he can log it in the tracker.
So which category do you fit?
Extra active QA
100% active while testing. These kinda QA's would exactly know where, why, when and how the application would crash.
Perspective QA
- Always things about how an end-user would use the application.
Quick QA
- This QA just tests certain main features and gets the build approved.
Verbal QA
- Tests the application and sits with the developer and discusses defects verbally and doesn't log it in the tracker.
High-per active QA
- Doesn't take breaks and always concentrates on breaking the code.
Social QA
- Always socializes with other QA and tries to gain knowledge from other QAs.
Abusive QA
- Doesn't like the product he is testing and always cribs about why he opted testing c.
Lazy QA
- Tests with zero enthusiasm. Run the application for 10 mins and gets involved with some other work.
Semi Active QA
- These kinda QA are good at testing but would be active in certain intervals of time.
Developer's boy QA
- This kind of QA's always inform about the bug to the developer and asks him if he can log it in the tracker.
So which category do you fit?