Whenever developer will recieved the defect from the
tester,then he will go thru the defect whether it is
acceptable or not?for that he will execute that application
again,while executing if he did not found any such type of
defect(what we are rise the defect above),then he will send
that defect to the corresponding tester with status
of 'reject',as a tester what we can do?(here writing the
reproduce steps and attached screen shots has been done by
tester while sending the defect to the developer, no need
to send reproduced steps and screen shots again)
- 6 Answers
- 8351 Views
- CTS, IBM, I also Faced
- E-Mail Answers
Answer Posted / varshab
In this case tester need to analyze bug once again.It may
possible that tester has made mistake while understanding
requirement.Wrong assumptions may lead to this
situation.Also while rejecting (will not fix) bugs developer
mention reason in bug tracking tool,tester should read that
& analyze it.If still tester is not agree then he/she can
discuss the same issue with his lead.After discussion if
tester still believe that its a bug then he can reopen that
bug & also add the descriptive report explaining how its bug.
| Is This Answer Correct ? | 2 Yes | 0 No |
Post New Answer View All Answers
tell me some major and minor defects in ur net banking project?
what types of bugs will we find out in banking projects
What is PBX Testing & What is Test coverage?
How to test the search functionality.For example in naukri advance search is there.how ca i test that page.
Explain thread testing.
I have to give weights to 5 stones so that using a simple balance and the stone i should be able to weight any number between 1-100
What is test closure?
What is a top-down and bottom-up approach in testing?
uses of checklist
what is test scenario and test condition?
Can you explain boundary value analysis?
How do you scope, organize, and execute a test project?
hi every one can you send me ISTQB Course material on my Email id deeptimundra997@gmail.com
what are your thoughts on SPRINT duration
How can software qa processes be implemented without stifling productivity?
