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?
Answer Posted / vinoth kumar
30. Its is the critical part of the Testing, since this is
the last test before delivering to the customers. Based on
the FSD document, the tester need to test whether all the
functionalites are working based on the customer
requirements or fulfilled the customer requirment.
There are two testing involved in Acceptence testing:
Alpha Testing
Beta Testing
Alpha Testing: This testing can be done in the developers
environment or the place where the SDLC done with the
presence of the business analyst along with the customer.
Beta Testing: This testing can be done in the customer
environment and most of the cases, from the customer end-
the end users will be invlolved in this testing.
Most of the cases it invloves to check the usability,
Navigation, Load and stress test.
| Is This Answer Correct ? | 1 Yes | 0 No |
Post New Answer View All Answers
Explain test driver?
what are the interviews questions for storage domain
What is coverage analysis?
what is enhancement Testing and how to perform enhancement Testing of any website
What is path testing?
What is a test configuration manager?
Explain compatibility testing?
What is failure?
Could anyone let me know what exactly is telecom testing & how is it done? And also how is mainframe testing done?
What is black box testing? What are the different black box testing techniques?
What are different SCSI command phases?
In the 7 Stages of the SDLC (Planning, System Analysis, System Design, Development, Testing, Implementation, and Maintenance), what is the INPUT and OUTPUT of each stage?
As part of which test process do you determine the exit criteria?
How would you estimate the amount of re-testing likely to be required?
I would like to know the kinds of questions that could come up with regard to backend testing? As i am new to this field would also know if backend testing is restricted only to sql and unix. If at all anyone has any information on the same kindly get back to me..thanks