Software Testing Interview Questions - 1


Q1. What is Software Testing?
Ans. Operation of a system or application under controlled conditions and evaluating the results. The controlled conditions must include both normal and abnormal conditions. It is oriented to detection.

Q2. What is Software Quality Assurance?
Ans. Software QA involves the monitoring and improving the entire software development process, making sure that any agreed-upon standards and procedures are followed. It is oriented to prevention.

Q 3. What are the qualities of a good test engineer?

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
Tactful and diplomatic
Good communication skills
Previous software development experience can be helpful as it provides a deeper understanding of the software development process
Good judgment skills

Q4. What are the qualities of a good QA engineer?

The same qualities a good tester
Additionally, they must be able to understand the entire software development process and how it can fit into the business approach and goals of the organization.
In organizations in the early stages of implementing QA processes, patience and diplomacy are especially needed.
An ability to find problems as well as to see 'what's missing' is important for inspections and reviews.

Q5. What are the qualities of a good QA or Test manager?

Must be familiar with the software development process
able to maintain enthusiasm of their team and promote a positive atmosphere
always looking for preventing problems
able to promote teamwork to increase productivity
able to promote cooperation between software, test, and QA engineers
have the skills needed to promote improvements in QA processes
have the ability to say 'no' to other managers when quality is insufficient or QA processes are not being adhered
have people judgement skills for hiring and keeping skilled personnel
be able to run meetings and keep them focused

Q6. What is the 'software life cycle'?
Ans. The life cycle begins when an application is first conceived and ends when it is no longer in use.

Q7. Tell us about some world famous bugs
Ans. 1. In December of 2007 an error occurred in a new ERP payroll system for a large urban school system. More than one third of employees had received incorrect paychecks that results in overpayments of $53 million. Inadequate testing reportedly contributed to the problems

2. A software error reportedly resulted in overbilling to 11,000 customers of a major telecommunications company in June of 2006. Making the corrections in the bills took a long time.

3. In March of 2002 it was reported that software bugs in Britain's national tax system resulted in more than 100,000 erroneous tax overcharges.

Q8. What are the common problems in the software development process?

Poor requirements
Unrealistic schedule
Inadequate testing
A request to pile on new features after development is unnderway.

Q9. What are the common solutions to software development problems?

Solid requirements
Realistic schedules
Adequate testing
stick to initial requirements where feasible
require walkthroughs and inspections when appropriate

Q10. What is a Quality Software?
Ans. Quality software is reasonably bug-free, delivered on time and within budget, meets requirements and / or expectations, and is maintainable.

Q11. What is good code?
Ans. Good code is code that works, is reasonably bug free, and is readable and maintainable.

Q12. What is good design?
Ans. Good internal design is indicated by software code whose overall structure is clear, understandable, easily modifiable, and maintainable. It should also be robust with sufficient error-handling and status logging capability and work correctly when implemented. And, good functional design is indicated by an application whose functionality can be traced back to customer and end-user requirements.

Q13. What's the role of documentation in QA?
Ans. QA practices must be documented to enhance their repeatability. There should be a system for easily finding and obtaining information and determining what documentation will have a particular piece of information.

Q14. Which projects may not need independent test staff?
Ans. It depends on the size & nature of the project. Then, it depends on business risks, development methodology, the skills and experience of the developers.

Q15. Why does software have bugs?

miscommunication or no communication
software complexity
programming errors
changing requirements
time pressures
poorly documented code
software development tools
egos - people prefer to say things like:
• 'no problem'
• 'piece of cake'
• 'I can whip that out in a few hours'

Also See:

1 comment: