I want to know how we should approach for testing real world objects. The problem that I faced before is to get the list of use cases from the interviewer. Whenever I asked what the real world object should do interviewer just say - the way you have used it. I personally prefer to have the use cases first. Is this a stupid question to ask what this product should do when we use that everyday? BTW, below is my overall approach for this type of question-
Here is my approach towards testing any real world object-
** Who will use this product and for what purpose?
** What are the use cases?
** What are the boundaries of use?
** What are the stress/failure conditions?
** What are the test cases? -- Based on the previous points we will create the test cases. And here we will do functional, integration, system, performance, stress testing
Please share your opinion, what is the best approach to handling this kind of question.