1. What are the properties of a good requirement?
2. Ho to do test if we have minimal or no documentation about the product?
3. What are all the basic elements in a defect report?
4. Is an A fast database retrieval rate a testable requirement?
5. What is software quality assurance?
6. What is the value of a testing group? How do you justify your work and budget?
7. What is the role of the test group vis-a-vis documentation, tech support, and so forth?
8. How much interaction with users should testers have, and why?
9. How should you learn about problems discovered in the field, and what should you learn from those problems?
10. What are the roles of glass-box and black-box testing tools?
11. What issues come up in test automation, and how do you manage them?
12. What development model should programmers and the test group use?
13. How do you get programmers to build testability support into their code?
14. What is the role of a bug tracking system?
15. What are the key challenges of testing?
16. Have you ever completely tested any part of a product? How?
17. Have you done exploratory or specification-driven testing?
18. Should every business test its software the same way?
19. Discuss the economics of automation and the role of metrics in testing.
20. 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.
21. When have you had to focus on data integrity?
22. What are some of the typical bugs you encountered in your last assignment?
23. How do you prioritize testing tasks within a project?
24. How do you develop a test plan and schedule? Describe bottom-up and top-down approaches.
25. When should you begin test planning?
26. When should you begin testing?
27. Do you know of metrics that help you estimate the size of the testing effort?
28. How do you scope out the size of the testing effort?
29. How many hours a week should a tester work?
30. How should your staff be managed? How about your overtime?
31. How do you estimate staff requirements?
32. What do you do (with the project tasks) when the schedule fails?
33. How do you handle conflict with programmers?
34. How do you know when the product is tested well enough?
45. What characteristics would you seek in a candidate for test-group manager?
46. 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?
47. How do your characteristics compare to the profile of the ideal manager that you just described?
38. 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?
39. Who should you hire in a testing group and why?
40. What is the role of metrics in comparing staff performance in human resources management?
41. How do you estimate staff requirements?
42. What do you do (with the project staff) when the schedule fails?
43. Describe some staff conflicts you have handled.
44. Is automation (or testing) a label for other problems?
45. Are testers trying to use automation to prove their prowess?
46. Can testability features be added to the product code?
47. Do testers and developers work cooperatively and with mutual respect?
48. Is automation is developed on an iterative basis?
49. Have you defined the requirements and success criteria for automation?
50. Are you open to different concepts of what test automation can mean?
51. Is test automation lead by someone with an understanding of both programming and testing?
|
