26). how will know do written test cases are sufficient to validate application

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?

Question Posted / sqt.qae

2 Answers
6154 Views
I also Faced
E-Mail Answers

Answers were Sorted based on User's Feedback

26). how will know do written test cases are sufficient to validate application of functionality? ..

Answer / 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

26). how will know do written test cases are sufficient to validate application of functionality? ..

Answer / deepika

26)By requirement specified in documents we came to know and
by traceability Matrix.

27)Test data is prepared by the specification provided by
business.

28) New, Open, fixed, Ready for Test, Close
New, Open ,Fixed, RFT, Reopen, close
New, Rejected
New, Deffered.

29)if devloper sccepts the defect , then he will change thed
defect status to open or fixed .

30)

31)Testing is stopped when all the major and critical
defects are closed.

80 % Testcases have passed.