1) Report Bugs in Manual Testing

How a tester report the bugs in manual testing?

There is multiple options in Quality center/Test director for identifying the defetcs in defetcs tab. 1.Suppose if you want know the overall defects in QC/TD just go to the defects tab with putting the filter condintion it will dispaly the all defects information then you can simply export all the defects to Excel sheet. 2.If you want know the status of Open/Retest/Fixed defects we need to put filter condition then QC/TD will give the corresponding defects only then you export all the defects to XL. 3. if you dont want all the colums in the defects there is good feature in the QC/TD for selecting the Particular column information of the defect. Ex: Defect number Defect status Detected by assigned to Detected date

2) Defect Not Related to TestCase When you find a defect which is not related to your testcase then what will you do?
When we find a defect which is not related to Test Case we will prepare the Test Case and raise the bug..... Bcoz the bug in the Bug Report has to trace the Test Case.
3)

How will you know whether your reported defect accepted are rejected?

1)One will definately log a defect in Defect tracking tool such as TTpro Little buggy with status open and assign to respective developer. 2)Satus will be new/open once you assign to developer then he will change the status of defect either fixed/deferred/.. and reassign to you.. from status changed by the developer tester will understand his dfect has been accepted or rejected.

4) What is the difference between testing and debugging?

Big difference is that debugging is conducted by a programmer and the programmer fix the errors during debugging phase. Tester never fixes the errors, but rather find them and return to programmer. 5) What are the components of traceability matrix?
Mapping the requirements against the test case is called as Tracibility Matrix. It means in order to tell the client that we have met all the requirements as specified in the SRS.

6) What is the difference between bug priority & bug severity?

Priority means how urgently bug is needed to fix Severity means how badly it harms the system 7) Who approved your test cases? It depends on the organization. QA Lead, if present, will approve the test cases. Otherwise, Peer Reviews are a good way of evaluating the test cases 8) How do you know when you have enough test cases to adequately test a software system or module?
U have to use tracebelity metrix which will check whether these testcases are covering all the requirement specification or any other functionality of the module or application is still left uncovered.

8)

What will you when you find a bug?

Once u find a Bug..check for what data it is failed..In which Environment..Better take a screenshot..Attach the screen shot with the particular testcase and fix priority and severity of the bug impact on the application and sent it to the developer if the Bug is non-repetable 9)

How do you determine What is to be tested?

This will be described in Test Plan. This will be decided by the QA Lead.

10) How to develop a test plan ? How to develop a test case?

Test plan document is prepared by the test lead with involument of tesing team in this document he specifices approach followed in the project Test cases are desigined by the test enginer after test plan is done when he design test cases he go through the FRS SRS and BRS documents By depending on the requirements he will design the test cses