Interested to Buy Any Domain ? << Click Here >> for more details...
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
- 9015 Views
- I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
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 |
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 |
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 |
differentiate defect age & build version control?
can any one help me? What is the Trecebility matrix ? what is that use and when it use and where it use
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?
what are the fields in traceablity matixes.
Can't we write test plan without any document with us or we definitely require the document for that
can you plz tell me the all documents to be completed by a manual tester?
How do you document well a website (i.e an ONG website) pls help me with a sample. Need your help UR
What is the difference between EXPLORATORY TESTING and ADHOC TESTING?
what will you do when your reported defect rejected?
How do we do testing if requirements are not documented properly?
can we test the product with out documents?
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...
Automation Testing 
