A good test engineer has a 'test to break' attitude, an ability to take the point of view of the customer, a strong desire for quality, and an attention to detail. Tact and diplomacy are useful in maintaining a cooperative relationship with developers, and an ability to communicate with both technical (developers) and non-technical (customers, management) people is useful. Previous software development experience can be helpful as it provides a deeper understanding of the software development process, gives the tester an appreciation for the developers' point of view, and reduce the learning curve in automated test tool programming. Judgment skills are needed to assess high-risk areas of an application on which to focus testing efforts when time is limited.
Actually that statement got me 118 hits on my search engine. It might be difficult to pin down the original source. But it should at least be accredited to anonymous. That is if Adhvik is not the originating author. Plus, I'm not comfortable with the first part of it: [ QUOTE ]
"A good test engineer has a 'test to break' attitude"
[/ QUOTE ]
Of course what I think is not all that important, however I do think a <u>GOOD</u> test engineer should have an open mind and not be a slave to finding bugs. His/her job is to insure that the application under test performs as it was designed and conforms to the needs of the users thus reducing the risk of release.
Success is the ability to go from one failure to another with no loss of enthusiasm.
~ Winston Churchill ~
Some basic and most important qualities are
1. He must be relentless, he must always keep trying to find news bug.
2. He must never be compromised with quality.
3. He must take everything as anew chalneg.
4. He must be very diplomatic as well.
5. He must be updated with all latest technologies.
6. He must think from customer point of view.