Interview Questions

Software Quality Assurance Interview Questions only (5)

Software Quality Assurance Interview Questions and Answers

(Continued from previous question...)

Software Quality Assurance Interview Questions only (5)

  • What are the properties of a good requirement?
  • Ho to do test if we have minimal or no documentation about the product?
  • What are all the basic elements in a defect report?
  • Is an "A fast database retrieval rate" a testable requirement?
  • What is software quality assurance?
  • What is the value of a testing group? How do you justify your work and budget?
  • What is the role of the test group vis-୶is documentation, tech support, and so forth?
  • How much interaction with users should testers have, and why?
  • How should you learn about problems discovered in the field, and what should you learn from those problems?
  • What are the roles of glass-box and black-box testing tools?
  • What issues come up in test automation, and how do you manage them?
  • What development model should programmers and the test group use?
  • How do you get programmers to build testability support into their code?
  • What is the role of a bug tracking system?
  • What are the key challenges of testing?
  • Have you ever completely tested any part of a product? How?
  • Have you done exploratory or specification-driven testing?
  • Should every business test its software the same way?
  • Discuss the economics of automation and the role of metrics in testing.
  • Describe components of a typical test plan, such as tools for interactive products and for database products, as well as cause-and-effect graphs and data-flow diagrams.
  • When have you had to focus on data integrity?
  • What are some of the typical bugs you encountered in your last assignment?
  • How do you prioritize testing tasks within a project?
  • How do you develop a test plan and schedule? Describe bottom-up and top-down approaches.
  • When should you begin test planning?
  • When should you begin testing?
  • Do you know of metrics that help you estimate the size of the testing effort?
  • How do you scope out the size of the testing effort?
  • How many hours a week should a tester work?
  • How should your staff be managed? How about your overtime?
  • How do you estimate staff requirements?
  • What do you do (with the project tasks) when the schedule fails?
  • How do you handle conflict with programmers?
  • How do you know when the product is tested well enough?
  • What characteristics would you seek in a candidate for test-group manager?
  • What do you think the role of test-group manager should be? Relative to senior management? Relative to other technical groups in the company? Relative to your staff?
  • How do your characteristics compare to the profile of the ideal manager that you just described?
  • How does your preferred work style work with the ideal test-manager role that you just described? What is different between the way you work and the role you described?
  • Who should you hire in a testing group and why?
  • What is the role of metrics in comparing staff performance in human resources management?
  • How do you estimate staff requirements?
  • What do you do (with the project staff) when the schedule fails?
  • Describe some staff conflicts you’ve handled.
  • Is automation (or testing) a label for other problems?
  • Are testers trying to use automation to prove their prowess?
  • Can testability features be added to the product code?
  • Do testers and developers work cooperatively and with mutual respect?
  • Is automation is developed on an iterative basis?
  • Have you defined the requirements and success criteria for automation?
  • Are you open to different concepts of what test automation can mean?
  • Is test automation lead by someone with an understanding of both programming and testing?

(Continued on next question...)

Other Interview Questions