Explain what is 'test plan driven' or 'key word driven' method of testing?
- 1 Answers
- 1423 Views
- I also Faced
- E-Mail Answers
Answer / Vivek Bharti
The 'test plan driven' or 'key word driven' method of testing uses predefined keywords to create test scripts that follow a specific structure. The tests are designed based on the test plan, and each keyword corresponds to a specific action or verification. This approach allows for easier maintenance and reuse of test cases.
| Is This Answer Correct ? | 0 Yes | 0 No |
Hi, I don't know exactly when System Testplan should be prepared 1)while analysing BRS or 2) analysing FRS or 3) after analysing the Requirement Specification
Could reviews or inspections be considered part of testing?
What is the maximum length of cable supported in SCS-1,2 and 3?
I am asked to create Usability testing methodology document, basically listing the Procedures & methodology to/for: a. Entry criteria Exit criteria for usability test b. Deliverables d. Methods of doing Reviews and inspection e. Methods of Reporting f. at which testing phase usability testing is done in v model Is there any sample document/template available on Internet? Any help will be greatly appreciated.
Hello Friends, I am one of the member in this group. I want to know that "Is there a future in Testing field (Black box Tester)". Do any of the Testing Genious can answer with explanation for my Query. sorry if i hurted any Testers by asking this type of questions.
This question is based on ages easy.
What is the difference between preventative and reactive approaches to testing?
What the main use of preparing a traceability matrix?
What is test/qa team lead?
What is cause-effect graphing?
Why we need localization testing?
26). how will know do written test cases are sufficient to validate application of functionality? 27). how will you prepare test data to validate input object? 28). explain defect status? 29). how will know whether the developer accepted you defects or not? 30). explain acceptance test? 31). explain when we stop testing? 32). explain scope of your project? 33). in which module you conducted testing? 34). explain defects which you found in that module? 35). if defect is not reproducible then what information you will provide to developer 36). if developer is not accepted your defect then what you will do?
Automation Testing 
