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

Is Test report same as Bug report....? I have to give Test Report to the client for my Application ....and as it started all of sudden i did not make the test cases and started of testing .....The bug Tracker where i report the bugs has a facility to download the Bug reported in word or in excel format....It has the detailed description of "version" of appliation tested, whom assigned .., resolved , closed..then the steps to reproduce the bug and all...Is the documnet test report...

2 Answers  


What is the Reporting Tool in java explain and give example?

1 Answers   Wipro,


Can't we write test plan without any document with us or we definitely require the document for that

5 Answers   ABC, Excel,


What is Test idea? format of test idea

3 Answers  


how will you report defects in your company?

8 Answers  






what methods will you follow to repare test cases in your organization?

3 Answers   CTS,


Test Documents Reporting answers

4 Answers   ABC, Mastek,


differentiate test strategy and test plan?

5 Answers  


if there are 10 step in test cases while executing if their is mismatch at step 5 what is status of test case ? pass or fail or anything else? if require tab is not available then what's the status of test case?

2 Answers  


what is the format of traceability matrix

3 Answers   DELL, IBM,


How do you document well a website (i.e an ONG website) pls help me with a sample. Need your help UR

0 Answers  


If you are working closely with business team, after receiving the requirements, if you think requirements need some changes, When will notice they need to be modified?,when will you approach them.exactly in what phase of SDLC?

4 Answers  


Categories