interview questions

[slayerrakesh]

1) what is a duplicate bug?
2) you dont have any documents, explain me how do you go testing?
3) what do you do if developer not accepted the bug?
4) how do you know that all test cases are covered against the requirements/?
5) tell me where QA people will be involved in sdlc?
6) test plan / test strategy? difference?

7) give me two reasons the bug has not been fixed by developer?
8) what qualities should have for a manual tester / automations tester

[slinkanand]

2) adhoc testing
3) test the bug with all valid conditions as per the requirement, if you find mismatch again then log the defect again with clear exaplanations as well as screen shots
4) by peer review process is one way, or by change requirement documents, or by traceability matrix or by bi-directional tracing
5) Quality assurance personnel are responsible for validating project assumptions and ensuring the quality of phase deliverables. Quality assurance personnel should be independent of the development process and use predefined standards and procedures to assess deliverables throughout project life cycles

[sundari]

8) for manual tester he can able to generate highyield test cases.for automation he should be familiar with all the testing tools like winrunner..............

sundari.a

[naveen_p25]

1) When the reported bug is similar to the previously reported bug then it is called duplicate bug. And developers will REJECT that particular bug.
6) Test Plan Document describes "What to test", Who to test", "When to test" and "How to test" of Application Under Testing (AUT). It is a project specific document and prepared by Test Lead.
Whereas Test Strategy Document prepared by Quality Analyst to define the required testing approach to be followed by testing team to achive the Testing Objective, It's a company level document.
7) If the reported bug functionality is not covered in FRS, developers treat it is as an enhancement and they may not fix the bug.
If they have no time to fix the bug they put it on hold and mention in release notes.