After asking the defect life cycle, if you think it is not a
valid defect, what you will do, whether you will store in
any document for future reviews,if yes, what is that
document, where you will save that document? or just reject
it and close it?

Answers were Sorted based on User's Feedback



After asking the defect life cycle, if you think it is not a valid defect, what you will do, whethe..

Answer / madhavi

If the tester thinks that is not a valid defect after
loging and before sending it to developer, tester can close
the defect by adding a comment saying "User Error" so this
defect can be closed.
We dont need to store any where once the defect is opened
it will be there in your defects list.

If the defect is send to dev then it will be rejected then
tester can close it.

Is This Answer Correct ?    6 Yes 2 No

After asking the defect life cycle, if you think it is not a valid defect, what you will do, whethe..

Answer / venki

Invalid defect should be tracked,thus it will help the
seniors(Lead/Manager)to identify the number of invalid
issues,it will further help the management/senior for
training programmes for the testers, pls correct me if i am
wrong.

Is This Answer Correct ?    4 Yes 0 No

After asking the defect life cycle, if you think it is not a valid defect, what you will do, whethe..

Answer / f

I think Venkini is right.

Is This Answer Correct ?    0 Yes 0 No

After asking the defect life cycle, if you think it is not a valid defect, what you will do, whethe..

Answer / atul mandlik

As a tester, if though i think that it is not a defect, i will look for the cause of defect, its severity on the module or requirement under test, possible defect multiplication in later stager if allowed to go through. Will report in defect log. Discuss with project lead or team lead. Then the decision on project lead / testing manager.
If its a minor and can be resolved in next version then assign it as deferred. if decision is that its not defect, then wil close it. if defect is similar to some previously documented defects, assign it as duplicate and look for steps to reslove it. all this info cab be viewed from defect log/report which can be excel sheet or word document or defect tracking tool such as bugzilla.

Is This Answer Correct ?    0 Yes 0 No

Post New Answer

More Test Documents Reporting Interview Questions

Hi Friends, Can any one tell me how the Risks for the basic web page testing in the Test Plan, as i am writting my first test plan. It will be greatfull if any one answer me as soon as possible

3 Answers  


what is your company testcase format?

18 Answers   Infosys, MasterMind, Sinsoft,


what type of documents needed in every phase of sdlc for SQA?

2 Answers   UHG,


HI, TRM(Test Responsibility Matrix) and RTM(requirement Tracebility matrix) both are same??

4 Answers  


After asking the defect life cycle, if you think it is not a valid defect, what you will do, whether you will store in any document for future reviews,if yes, what is that document, where you will save that document? or just reject it and close it?

4 Answers  






Need information on Documentum4.3, any websites. What is this Documentum,how to access,features and benefits. ASAP Thx.

1 Answers   Cap Gemini,


how will you decide defect severity & priority?

14 Answers   Hewitt,


What is the difference between EXPLORATORY TESTING and ADHOC TESTING?

4 Answers  


What is Defect/Bug/Error Life Cycle?

11 Answers   Covansys, Hewitt,


how many levels of regression testing is avilable in our testing process?

4 Answers  


can any one help me? What is the Trecebility matrix ? what is that use and when it use and where it use

6 Answers  


What is reporting hiearchy in testing? Who report to whop and complete hiearchy including developers

6 Answers   ABC,


Categories