5.

Did you have a situation where you did not have any documents (no requirement
document, no Use Cases, or no Design Document) and you had to write the Test Ca
ses? How did you write the Test Cases in this situation?
Answer: Yes. I have been to that kind of scenarios several times. There were co
mpanies where they had no documents at all. In that case, I had to discuss the a
pplication scenario and functionalities with the Business Analysts or developer.
On the basis of that discussion, I prepared a document in consultation with Bus
iness Analysts and Developers and then started writing Plans and Test Cases.
6. What you worked with Use Cases before?
Answer: Yes. I have written Test Cases using Use Cases.
Can you tell me what a Use Case is?
Answer: A use case is a document that describes the user action and system resp
onse for a particular functionality.
8. What is Business Requirement Document (BRD)?
Answer: It is a document that describes the details of the application function
alities which is required by the user. This document is written by the Business
Analysts.
9. What is Business Design Document?
Answer: It is the document that describes the application functionalities of th
e user in detail. This document has the further details of the Business Requirem
ent Document. This is a very crucial step in Software Development Life Cycle (SD
LC). Sometimes the Business Requirement Document and Business Design Document ca
n be lumped together to make only one Business Requirement Document.
10. What is a Module?
Answer: A Module is a software component that has a specific task. It can be a lin
k , which can go inside to its component detail. (This is NOT a very common questi
on for the interview. This is just for your knowledge, if you don t know what a mo
dule is.)
11
. What is walk-through meeting?
12. What is a Use Case and what does it include?
Answer: A Use Case is a document that describes the user action and system resp
onse for a particular functionality. It includes cover page, Revision History, T
able of Contents, Flow of Events (normal flow and alternative flow), Exceptions,
Special Requirements, Pre-conditions and Post-conditions.
13. What is Build?
Answer: When each of the different modules of software is prepared, the Configu
ration Management Team (CMT) puts them in a single folder and it is called the Bu
ild . . (This is NOT a very common question for the interview. This is just for yo
ur knowledge, if you don t know what a build is.)
14. What does the Build Deployment mean?
Answer: When the Build so prepared by the CMT (Configuration Management Team),
it is deployed (put) to different Test Environments, it is called the Build Depl
oyment.
15. What is Test Strategy?
Answer: A Test Strategy is a document that describes the test efforts, test conf
iguration, testing tools to be employed, test environments, exit criteria and en
try criteria for testing, what different types of testing will be carried out (f
or example, smoke test, regression, load test, functional test and so on) types
of testing to be carried out and system requirement. The Test Manager or Lead wr
ites it. (Remember, the Tester does NOT write Test Strategy. A Tester writes Tes
t Plans and Test Cases)