Interview Questions and Answers for QTP (Quick Test Professional)

Thursday, August 04, 2005

How does one make a good tester ?

For starters, formal training and gaining experience in both:
1. Manual testing, and
2. Quality Assurance

1. Understanding of systems and software
2. Programming skills are helpful

Skills a good SQA person has to have:
- 'test to break' attitude,
- Ability to take the point of view of the customer,
- Strong desire for quality,
- Attention to detail.
- Tact and diplomacy are useful in maintaining a cooperative relationship with developers,
- Ability to communicate with both technical (developers) and non-technical (customers, management) people
- 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.
- Judgement skills are needed to assess high-risk areas of an application on which to focus testing efforts when time is limited.
- You must be able to understand the entire software development process and how it can fit into the business approach and goals of the organization.
- Ability to understand various sides of issues
- Patience
- Ability to find problems as well as to see 'what's missing' is important for inspections and reviews.
- Tenacity
- Resourcefulness
- Team spirit

- Salesmanship
- Ability to learn quickly
- Ability to research
- Perseverance

QTP and Winrunner Questions and Answers
Contact: qualityvista @

Post to: IpadIt! | blinkbits | blinklist | Blogmarks | co.mments | | | digg It! | Fark| feedmelinks | Furl | LinkaGoGo | Ma.gnolia | Netscape | Newsvine | Netvouz | RawSugar | Reddit | scuttle | Shadows | Shoutwire | Simpy | Smarking | Spurl | TailRank | Wists | YahooMyWeb!


At 2:44 PM, April 29, 2006, Blogger Pradeep Soundararajan said...

could you let me know why a tester should have a 'salesmanship" ?

At 9:33 AM, May 15, 2006, Blogger Techie said...

In my opinion, a tester needs to have 'salesmanship' to sell his defect to the developer in order to get it fixed. When you log a defect for a project, it depends on how you write the defect to convince the development team that this defect should be fixed. You could focus upon the impact of the defect on release schedule/stability/sales of the product, whichever applicable. Once you 'sell' your defect to the development team, they would be keen on fixing it.

And, in many companies, few of the criterias to evaluate a tester's performance are 'how many critical defects he/she logged?', 'how many defects logged by him/her were fixed by dev team?' etc.
So, 'salsemanship' becomes an important characteristic to have for a tester.


Post a Comment

<< Home