Many myths abound, such as being
creatively sadistic or able to handle dull, repetitive work. As a one-time test manager and currently as a consultant to software development and testing organizations, I've formed a picture of the ideal software tester-they share many of the qualities we look for in programmers; but there are also some important differences. Here's a quick summary of the sometimes contradictory lessons that I've learned.
I feel a good Test Engineer must have the following qualities:
1.First quality that the test engineer should have is "Attention to Detail"
2.Test Engineer should have a Customer savvy attitude
3.Should have a Test to Break attitude
4.While testing Should think end user perspective
5.Should communicate the defect findings properly
Just to make a small change to what you said above , "A good tester is one who understands and meet the expectations of good stakeholders" :) ( Unless, the bad stakeholder doesn't have authority to fire or deny a hike or promotion )
The “ideal” test engineer :
knows all about his feature area …
… and supports requirements engineer with feedback to specs (testability)
knows whole system …
… and validates system with complex tests based on use cases also
has domain knowledge …
… to keep the end customers expectations
is testing efficiently …
… finds the balance between feature coverage and hot spots
communicates with all his counterparts …
… is informed about the project and informs his colleagues
Be destructive during the test, …But be constructive in your support to solve the problems found....
If you don’t find the remaining fault, the end-customer will find it...
Finding faults is NOT to blame colleagues …---> … it’s to HELP them to improve their results
Report all faults detected, DON’T accept a severe fault to be played down
System-Test can concentrate on function-, stress-, stability-tests, prove of concept, combined-tests and duration-tests