1. Bugs
   1. Focuses on important bugs
   2. Finds bugs based on different quality criteria
   3. Tries to find the root cause & not just the symptom
   4. Does not consider bugs as a measure of quality
   5. Attacks the issue and not the programmer
2. Knowledge
   1. Works on building domain knowledge
   2. Interested to know entire product & the interactions
   3. Learns about testing approaches & standards
   4. Learns about code
3. Communication
   1. Good communication skills
   2. Answers questions by different stakeholders
   3. Doable, Quick, In-Depth Answers
   4. Doesn't waste anyone's time
4. Attitude towards programmers
   1. Understands that coding is difficult
   2. Respects the programmers' skills & expertise
   3. Eager to work with them & produce great quality work
5. Bug Reports
   1. Good bug advocacy
   2. Detailed bug reports
   3. Provides proof and tests conducted
   4. Mentions tests done while verifying bugs
6. Feedback/Quality
   1. Provides feedback to programmers
   2. Owns their share of quality
   3. Does not mislead anyone
   4. Highlights stakeholders with important information